MacWorld 1998 May

home *** CD-ROM | disk | FTP | other *** search

/ MacWorld 1998 May / Macworld (1998-05).dmg / Serious Demos / Lasso 2.5 Test Drive / UserGuide / LDML 2.5 Reference v1 (.txt) < prev

Wrap

FileMaker Pro Database | 1997-12-12 | 528KB | 9,985 lines

work makAll play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All HBAM2016AUG95 Pro 3.0 All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a goodCopyright 1984-1997 Claris Corporation good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. All play and no work makes John a good boy. field displays number fields specif@ conjunction doscript create button@ applies assist command@ consists@ criteria defined displayedu elsez entries@ examples found html&-skiprecords@ inliney larger@ layout1&-token@ minutes@ namep opend otherW parameters random&-database@ referrer@ required selections@ should substitution text1234some delete action deletes specific record specified@ HBAM3016AUG95@ actionv activity error replyB recordA addressE applek apple eventk arguments backgroundU begin begin logical operator beginningC beginning numberC breakse browserH checked clientE client browser typeH client domain addressE client addressF client passwordG client usernameI coden commentt concatenate conditionalu conditional statementu contentJ content typeJ cookieK count current databaseL databasesO decodeP decode deleteQ delete recordQ delete replyR detailS detail linkS displayK display layout names display databasesO display cookieK Pro 3.0 - 4.0F! USENGLSH.MPR USER.UPR display current display current display database layout display database nameM display field namep display field searched display lasso action{ display layout display values display logical operator display maximum records value display display databaseN display previous display referrer display repeat value display response display search arguments display search operator display search value display server display records value display field display order display parameters display token value display total records domainE duplicateZ duplicate recordZ duplicate reply[ email^ email email email format` email froma email hostb email subjectc email encodee encode breakse encode htmlf encode encode smarth encode logical operator endingj ending numberj errorB eventk event error stringl event resultm event result coden execute execute filemaker script extract field fields filex filemaker findq recordsq random record script post-lassoT script post-lasso backgroundU script pre-lassoV script pre-lasso backgroundW script pre-sortX script pre-sort backgroundY formr parameter valuer format` found froma group headers hostb htmlf commentt https headers imagev image actionv includex include filex inline inline resultz insert lasso{ lasso process| layout layout leading length linkS lists activity logical logical operator count lower math-add math-divide math-modulo math-multiply math-round math-round result math-subtract maximum maximum records missing nameM names record group results reply nothing numberC number record shown number records found openN operator options options selection order parameterr parameters passwordG portal position post-inline post-lassoT pre-lassoV pre-sortX previous previous record group process| random recordA record display record record value recordsq records referrer remove repeat repeating repeating fields repetition replace replyB required required field required field missing response resultm results retrieve retrieve variable returned scriptT search searched selected selection server cookie value variable token record shown returned records smarth field order specifyL specify databaseL specify layout statementu stringl string concatenate string count fields string extract string position string field string insert string length string lower string remove string remove leading string remove trailing string replace string upper subjectc submit} submit password} submit username~ timeout token total trailing typeH update update record upper usernameI valuer value lists values variable while action command container sub-container substitution action{ adderror addrE backU begnum breakse checked clientE client addrE client client passwordG client typeH client usernameI commentt concatenate contentJ content typeJ cookie count countfields database database nameM nameN namesO decodeP decode delete deletereply detailS detail linkS doscriptT doscript postT doscript backU doscript doscript backW doscript presortX doscript presort backY duplicate duplicatereply emailbcc emailcc emailformat emailfrom emailhost emailsubject emailto encodee encode breakse encode htmlf encode encode smarth encode endnum errorstringl event event errorstringl event resultm event resultcoden extract field field namep findall findposition formr paramr getfield header htmlf commentt image include inline inline resultz insert lasso{ lasso action{ lasso process| lassopassword lassousername names layout layout length linkS value logicalop logicalop value count lowercase math-add math-div math-mod math-mult math-round math-sub maxrecords maxrecords value nameM namesO nfound noresults nothing nshown opbegin opend operator option order paramr passwordG portal postT inline presortX process| random recid recid value record records referrer referrer remove removeleading removetrailing repeat repeat value repeating repetition replace reqfieldmissing required response response resultm resultcoden scripts search search search field search search value selected server server server server cookie skiprecords skiprecords value smarth field order sortfield sortorder string string concatenate string countfields string extract string findposition string getfield string insert string length string lowercase string remove string removeleading string removetrailing string replace string uppercase timeout token token value total total records typeH update uppercase usernameI value value while 0.001 1/1/97 10&-logicalop 10&-maxrecords 11/21/97t 12&photov 12312312some 1231234123and 123456 126.0 1345.12354 1345.124 1345.75 1345.8 1355.12 1355.1234 17005z 19.42 1yadda2yadda3yadda4y 20&-sortfield 20.12 20000 20database&-layoutA 20date 20formatS 20isP 20layoutS 20layout&-responseA 20morei 20responseS 20somei 20stringP 20texti 250.0 29.42 29.50 2f202.252.25.63emploi 2f84&-skiprecords 2fdetaili 2fhitlist 3ethP 4123and 60&-findall 60&-search required field assist completion single record filemaker database duplicateZ specific record filemaker database identif token value format abbrev abbreviation abbreviations abilityT ableS aboutB aboveK absolute accept acceptsK accessI accessed~ accessibilityp accessingH accommodatet accomplish accomplished accordingb accumulate accumulate&-scripts acgiA achieve actionA actionb actionsT activated active activityM actualo actuallyH add&-databaseA adda1yadda2yadda3yad addedB adderrorB addingB additionT additionalw addrE addressE addressesb addsA adjust admin~ admin&-lassopassword~ advantagex affects afterK after cookie value browser cookie again against~ agentH airlines alias alignv all&-sortfieldq allocated allow{ allowingh allowsJ alongp alsoA altered{ alternatively although alwaysx amountw ampersandsL example follows trailing spaces removed anchoro and&-timeout and/or anglef angledh anotherA anythingy appearA appeared appearing appearsJ applek applicationT appliedi applies applies applye applying approach appropriate areat arguments aroundK arrival lasso processes response format database lasso processes response format layout ascendingq assetsu assignedb assist assist associatedD assume assumedT attemptsI attribute attributes authenticationI authoring auto-enteredB auto-populated automaticallyS availableE avoidL backT backgroundU basedM basicI bccreceiverb bccreceiverdomainb becomes becomes beenD beforeT beginA beginning begins begnumC behaviorx beingH belongo bestw better betweenS bigserver bit-depthw blankB booleanp borderw brackett bracketsf breako breakse bringsV broughtT browse browserE browserss browsertypefield business~ business&-layout~ buttonA buttonsA bytes calculation calculations callS calledS callss cancelQ cannotq capital carbon^ carriagee carried carriesy carrys case^ case-sensitiveL casest categoryy cause ccreceiverb ccreceiverdomainb cells certainT changeM changedp changingx channels characterg charactersL checkK checkboxT checkboxesD checkedD checking~ checks~ choice choices cities clarifyK clear click clicks clientE client'sE clip2gifw clone closingt codes coded colonK colored com/project/add combination combinex combinedu combiningA comeso commaT comman commandX commandsb commasP commentt commentedt commentst communications compareu comparisonu comparison-valueu compatibilityx compatibleH completeo completedB completely completes completionV complexu complicated compressionw computer concatenateP concatenated concatenates concatenationu conditionK conditionalD conditional statements number repetition conditionals conditionsu confirmQ conflict confusedy confusionL conjunctionT considerationsq consideredx consistency consistsu constructedS constructingx constructiony contactso containP containedb containerD containingB containsr contentJ contentso continuesu controlo controlled controls converth convertedw cookieK cookiesK cookies pieces information saved browser setti copy^ corresponding couldA countp counted countfields countries course coverx createM createdB createsS creating criteria criteria cross currentI currentlyD currentrecordid currrentlyZ cursor customB customized daother dashesy dataA databaseA databasenamefield databasesO datet date/timep dates decimal decodeP decode 20string decoding defaultB defaults define definedq defined deleteQ deletedQ deletereplyR deletesQ delimiteds delimiter deliver deliveredb delivers demonstratedx dependingp dependso depthw descendingq describedk description} designateu desiredp destinationb detailS detailsD determineD determinedM determinesu determining dialogI differentT differsy directQ directed directlyw directories directory displayK displayedB displayedu displayingC displaysp divide divided division documentv doesP domainE domainaddressfield don'tT doscriptT drainT duplicateZ duplicatedZ duplicatereply[ duplication[ during dynamicallyx dynamo&-layout eachP earlierx eitherS elementD elementsA eliminate elseK elsez elsewhereA email^ emailbcc^ emailcc_ emailformat` emailfroma emailhostb emailsubjectb emailto^ embeddedS employee employeesx employees&-layoutA employees&-recidv employees&layoutz employees/actionv empty enabledE enables encloseu enclosedt enclosing encodeA encodedA encodeso encodingK encounteredB endifu ending endnumj enough enter enteredA entireu entirelyy entitiesf entriesB entry eq& eq&namer equalu equals equivalentw erraenosuchobjectz errorB errorsB errrequiredfieldmissz especially essentially establishedS evaluateu evaluatedu evaluatesu evenA eventk everyx everythingo everything between record record container exact~ exactsearchq exampleA example/next examplesw examples except executeT executedT executing existingB exists expense expenselist expire expires explorerH exported expressionu expressionsu extendedL extra extract extracted extracts fails falseK fashiony faster favorite feature fewer fieldA field'sp field-level fieldnameA fieldname1 fieldname2A fieldsA fifth fileB filemakerA filemaker scripts forms themselves filenameS filesK finalS findq findallq findall&-databaseq finding findposition findsq finished firstC five^ folderN followedu followingA followsA footerx example equivalent remainder example simply foregroundV formA formatI formatsS formattedb formatting formparam formsT foundB found fp3&-layout fromE frontT frontmostT fulfill fully function functionality functions future gather generalo generallyS generatedM genericB getfield giveL givenq gives globalx globally goahead~ grabs graphicv graphicsw great greateru greatest| groupC grouped groups guest guidek handy hard-codedu haveZ having headerH headerss heightw here'sJ hiddenQ hitlistQ holding horizontally host^ hours howeverK hrefA htmlA html&-maxrecordsq html&-op~ html&-recid html&-show html&-skiprecords html&A httpH https hypen hyperlinkb hyphen identified identifier identifieso identifyQ token using token lasso subst lasso security initialized lasso check access~ ignoret ignoredJ imageA imagesA imbeddedh immediatelys importanty imposed includeB includedJ includes includingf incorporated incorrectz increase increased increases increasing incremented indicateT indicatedT indicatesR infoN informationE initialized~ initiallyi initiatesb inlineb inliney inlinesy inputA input submit nothing value submit insertS inserted{ insertedyadda1yadda2 insertfieldo insertion insertsF inside installedk instanceo instances insteadz instructA instructsD intelligentx interacty interchangeableD interlacedw intermediaryw internetH intoA invoke{ invokedX ipnumberfield outside inline reportz itemD itemsD january javascriptQ javascriptst jobsy johnz john&searchz jpegw jpeg&-imagev justb keepS keeping keepsU keywordp knownH largeT largerw lassoA lasso ability automatically email messageb lasso ability directly serve filemaker picturw lasso insert represents lasso'sx lasso-action lasso-processedP lasso-returned lasso-servedI lassoactionfield lassopassword~ lassousername} lastj latin-1g launchedN layoutL layout1&-token layouts leading leads~ leastb leave left^ length lessu letters levelb liabilitiesu limit limitedB limits lines lines linkA linking links listB listedQ lists literalP literalsu loadss locate locatedN locates locations logged logicalu logicalop loginb login/emailb longb longerT lookupB lookupsE count repeat value clear looping lowercase macintoshH mader made-upr mailb mainA main&-responseS makeS makingx manipulation mannero manual manuallyS manyT markets matchB matches math-add math-div math-mod math-mod math-mult math-round math-sub matter maximumq maxrecordsq meaning meansu measured memory menus messageB methodA microsoftH mightx mindS minimum minute minutes missingz mixed-case modifiablep modifiedp moduleN modulesN modulo monday month moreB mostD most-nestedu mozilla/2.0H mozilla/3.0H msieH multipleP multiply mustA nameA namep name&-layout name&-response namedS namesL navigatorH nearest needS neededt needsQ nested\ netscapeH nextu nfoundu noerrz non-interlacedw non-relativex noneT noresultsz normally noteB notesx nothingb notification^ nshown numberB numbered numberingp numbers numericC object occasionsT occurx occurredz occurrence occurrences occursB oldert omitted onlyC opbegin openN opend opend openingt operatey operatoru operators opportunityQ opposed optionA optionalK optionallyK optionsu number portal orderC original| originally otherA otherW others otherwiseT outputF output outputs outsidez overrideJ pageB pages painlessx pairq pairedr pairing pairsS paramr parameterA parametersK parameters paramnamer paramterr parentheseso parenthesisK partA particularr partition passh passedb passes passwordI passwordfield pathK pathsx pattern perception performL performance performedQ performs periodT permissionZ permissionsq personH phone phonefield photov pictw picturew picturesw piece pieces pinpointH pixelw placeD placedS places placingp plug-in plusA pointv pointsy pop-upT populate populatedo portalo portal portals portion position possibleB postA post-lassoM power powerpcH practiceH pre-lasso precedence precision predetermine predetermined preferred presentQ preservet presortT pressing preventy prevents previousM previouslyS price primarilyt primary printed priorT privileges~ problemB problemsK processA processedb processesM processes script after other specified lasso actions processes script before other specified lasso actions processes script before other specified lasso actions processes script before lasso command invoked processingU produceD productlist products programw programs prohibits projectA promptedI promptings promptsQ protectedI protectionp protocols provideQ providedB providesi provisions pull-down qualityw quickx quickery quotesK radioD random random&-database randomly rangeC rathery re-imported re-launchedx reaches readp readsB realmI realm-basedI reasons recalled receive receiverb recidQ recognizes recognized recommendedx recordA recordsC recreatingp redirects redirectings redirectss redoes referD refer client username refer notes description referenceL referencedM references referer referred referrer referring referringpage reflect refreshings rejected relatedo relationship relationshipnameo relativeb relevantD reloadings remainder remainingy removeP removed removeleading removes removetrailing repeat repeateds repeatedly repeatiing repeating repeating yourfieldname repeats repetition repetitions replaces replacedo replacedother replaces^ replyA reportH reported reportsz representing representsp reqfieldmissingz requestA requestss require~ requiredL required requiresB requiringT reset resettings responseM restA restrictionq resultD resulted resulting resultsq retired retrieveK retrievedK retrieves retrievingQ returne returnedA returning returnsD revertx rootb round rounded count field contacts rulesx runningT sameC sampleA satisfactoryw saveds saves scriptT script1T script2T script3T scriptsT scroll scrolling searchS search&-databaser searched searchesr searchgraphicA searching secondr secondary seconds secure securityI description lassousername selectT selectedD selectingA selection selections semi-colon send^ senderb senderdomainb sense sensitiveu sentH separateT separatedP separately separating separator sequences seriesu serveu servedx serverE server abbrev display server short display 1/1/97 server's server-side servingb setsv settingx settingsE setup severalu shaded shift shortu shouldL should show{ shownK showsA sideu signA similare similarlyy simpleT simplifyu simplyD sinceD singleS single-field siteH siteidK sizeT skipped skiprecords slash slashesL slowing smallerw smarth smith social solution somei someone somethingT sortH sortedT sortedby sortedfield sortfieldq sorting sortorderq sortsT sourceS spaceK spacesA specialL specificB specification specifications specifiedA specifiesL specifyA specifyingr squareo standardo starts starting state statementD statementsD statuss still~ storedp stream~ street stringP stringanother strings stuff sub-container sub-section submitA submittedT subsequent subset substitutey substitutedE substitutes substitutionC substitution subtract subtracted successz successfulR successfullyz successive suchP summaryA suppliedx suppliesx support supportedT supports sureA surroundK surroundedP surrounding switchM symbolu symbolst synonymous syntaxA table tables tabular tagging tagsD take{ takenE takesT targeted tasks tells temporary tenth testy textA text/htmlJ text/sgmlJ text123123123 text1234123123 text1234some text1234some text12some textsome thanu thatB action record specified filemaker adderror specify custom error apple event installed apple event installed commanl checked instructs lasso place checked parametD client substituted visitor's domainE client inserts client's address client inserts browser visitor client username inserts current content substitution allows override current action inserted reply database specifies which filemaker database lassL within names names names retrieve names decode substitution encoding tagsP delete action deletes specific record specifiedQ deletereply indicates which reply format detail creates specific record duplicatereply specifies reply format valid within container valid within container emailbcc optional emailcc optional emailformat lasso email that` emailfrom lasso email emailsubject lasso email emailto lasso email encode smart substitution encoding encode substitution encoding tagsi event described lasso guidek field displays number fields specifp field indicates which field should substituted findall action finds records specified filemaq header determined using header header image action usually specified other actiov include substitution combine another inline result reports success action lasso container control displayeu lasso process instruct lasso proce| within names names retrieve names layou layout instructs lasso which layout value return value items allows information about current lasso actio logicalop value display parameters display current date@ encode html@ layout records string remove leading@ client type@ include@ replace@ 20isP actionb applies assist command@ consists@ criteria defined displayedu elsez entries@ examples found html&-skiprecords@ inliney larger@ layout1&-token@ minutes@ namep opend otherW parameters random&-database@ referrer@ required selections@ should substitution text1234some delete action deletes specific record specified@ field displays number fields specif@ count outputs number representing current@ operator command determines lasso compare search display operators applied string countfields string substitution nshown displaying rang@ theseT timeout tuesday@ utilities@ viewed@ which within conditions@ display displays specified database@ displays value existing cookie lasso format finds records filemaker database@ inserts output html@ logical@ outputs number current repeat containers record@ returns@ shouldL specifies result apple event@ count outputs number representing current instructs lasso display math-add values value math-div divide values math-mod divide values output math-mult multiply values toget math-round round value nearest math-sub subtract values maxrecords limits maximum number records maxrecords value display parameters display links noresults delivers specified result nothing action instructs lasso process opbegin opend command create opend field-level operator there operator command determines lasso compare option format fields contain parameters described follows portal portal display multiple inline allows execute actions after previous allow through random action finds random record specified referrer display referer repeating repeating repeat value required require someone enter response retrieve response indicates format scripts action conjunction doscr search action completes specified filemake search field display field search display operators applied search value display value entered selected instructs lasso place selected param server inserts current output server inserts server inserts current output value named variable action displays search forms auto-popul skiprecords specified number skiprecords value display parameters field display field order sub-container display order sortfield tells lasso which field result sortorder applies sortfield appears string concatenate substitution string string countfields string string extract string module string findposition string string getfield string modul string insert string module string length string module string lowercase string string remove string module string removeleading string string removetrailing string string replace string module string uppercase string substitution begnum displaying numeC substitution endnum displaying numej substitution nfound displaying substitution nshown displaying substitution total records display between search search container between container timeout timeout value update action updates specific record specified value value display value current record substituted recid value which submitted lasso action theirf themS themselvesT thenC theoryH thereB there three instances which variables great therefore thereinb these theseT theyT thing{ third thisA example would output string count encoding module retrieves indicated variable display thoset thoughB threes three-letter throughb throughout thusZ timeQ timeout timeout times title repeat values numbered togetherP tokenS tokens totalp totals track trailing traits transformedz transformsy translatee transmitted travel triesq troubleshooting trueK tuesday twice typeA types typicalb typicallyS unable unavailableT under underscore understanding undoP unfortunately uniqueB unknownp unlessz unnamedP unselect unsortedq unsuccessfulz untilu updateS updatedZ updatesx updating upono uppercase url-encodeK url-style urlsy logicalop command select operator usedA usefulD usefulnesst userH useridr usernameG usernamefield usess usingA usuallyv utilitiesi utility| valid\ validation valueA value1u value2u value3u value4u value5u valuelist valuesB values added filemaker repeating fields variable variables variation] variations variousT versions versionsS vertical vertically veryT viewS viewed violationZ visibley visit visited visitorH visitor'sE visits wantA web&-response web&usernamez web-serving webstar wednesday wellt wereB whatH whatever whatever found between while while whenB include included another lasso wheneverb whereo whether whichB which whileH while processing format lasso perform additioy whoseo widthw willA window withA withinD within withoutT won't wordsP workS worksX wouldA written yadda yadda12yadda3 yadda12yadda3yadda4y yadda12yadda3yadda9y yadda1yadda2yadda3 yadda1yadda2yadda3ya yadda9yadda0 yaddainserted1yadda2 yieldsw youfilenameq yourH yourdbname yourdbname&-layoutq yourfieldnameS yourlayoutnameq yourscriptnameT yourtokennameS about actionL actionsy added\ addingB additionaly addressF addsA values record specified filemaker databaseA afterR allowsJ allows information about current lasso action either allows override default content text/htmlJ anotherx applek applied appliese associated auto-populated before beginning being{ blind^ breakse browserH button carbon^ characters checkedD client'sF coden combinesx combines another format processed lassx commentst compare completes completes specified filemaker database concatenatesP concatenates specified removes encoding concatenates specified returns lowercase concatenates specified returns uppercase concatenates specified applies lasso concatenates specified encodes concatenates specified encodes concatenates specified together applies concatenates number unnamed parameters condition conditions\ conjunction contained containerD containers contentJ contentso controls\ controls conditions displayed included cookieK copy^ create created createsS creates field-level logical operator creates specific record databaseS creates imagev currentG currentlyN custom databaseA databasesO defaultJ deleteR deletesQ deletes specific record databaseQ delivered deliversB delivers specified results found delivers specified problem encountered withB determiness determines lasso compare entered value determines header informations display display display created displayed\ displaying displaysC displays database field's namep displays search forms auto-populated values displays repeating values specified database displays image database fieldw displays contained items specified number times displays client's addressF displays contents fieldo displays current passwordG displays current usernameI displays ending number range found recoj displays multiple portal database layout displays currently databaseN displays field search findall displays field current displays specified databaseM displays specified layout conjunction displays names currently databasesO displays group found records displays numeric range found recordsC displays operators applied field searc displays order current found displays parameters previous search displays previous group found records displays previous created displays referer created referer displays result inline actionz displays total number records found displays total number records subset returned displays value entered specific field search displays value associated specific record displays value existing cookie lasso format displays visitor's browser typeH displays visitor's domain nameE divide divides divides values domainE doscript duplicatesZ duplicates recordZ duplication[ either elementD elements email^ encodesf encodingP encounteredB endingj field-level operator entered errorl eventk every execute existingK extracts extracts specified range characters source fieldo field'sp field-level fields fileB filemakerA findall findsq finds random record database finds records filemaker databaseq finished formatK forms foundC fromP given group headers hitlist htmlD httpr imagev included\ included order lasso email message after indicated^ informations inlinez insertsr inserts represents referring inserts current output inserts current output inserts current values repeating field inserts output inserts specified string source string inserts total number records database inserts value current record inserts value token reply inserts variables inserts values previous submission instructs instructs lasso which layout specified instructs lasso process datab intoD itemsD lassoK layout layouts limits limits maximum number records displayed hitlis linkS listD locatedt logical lowercase matches maximum message^ missing multiple multiplies multiplies values nameE named namesO nearest numberj numericC occurrences offers offers option repeat given openN operation operator operators option\ order` output outputs outputs number current repeat containers outputs remainder divide operation overrideJ page{ parameterD parameters| passes passes value format without passing passwordG pattern performL performsy performs additional lasso actions within format filey placesD places checked parameter element places selected parameter element pop-up portal position post-lasso previousr problemB process processedr processest processes located within commentst processes specified parameters displays result| random rangeC recordA recordsC referer referring remainder removesP removes specified range characters source removes occurrences specified pattern which removes occurrences specified pattern which repeat repeating repeats repeats display elements every record returned repetition replacement replaces replaces specified specified replacement replyR represents required requires requires values entered field before response resultm results retrieves retrieves specified retrieves names layouts specified database returnedl returns returns value items field specified using returns numeric position beginning specified returns value field returns total number fields specified rounds rounds value nearest value scriptT search security} selected selection selects selects operator search send` sends^ sends blind carbon email message email sends carbon email message email address_ sets} cookie password lasso security} lasso response username lasso security~ value named variable should shouldL skipped skips skips specified number records displaying smarth source specificQ specifiedA specifiesL specifies custom error delivered require specifies database record specifies apple eventk specifies error string returned apple eventl specifies which filemaker database lasso should perfoL specifies filemaker script specifies format displaying results specifies number repetition within record repeati specifies reply format successful record dupl[ specifies reply format after successful specifies result apple eventn specifies result apple eventm specifies order specifies which field results stringP strings submissionr submitted subset subsitutes subsitutes number maximum number records substitutes{ substitutes current action being processed{ substitutes layout previous lasso action substitutes number records skipped retur substitutes parameters previous search subtracts subtracts values successfulR tagst taken` targeted textP text/htmlJ thatf inline allows execute actions after thene through times togethere token total totals totals number characters specified string typeH unnamed updates updates specific record database updates fields pop-up selection post-lasso uppercase conjunction doscript create button usernameI usingD valueD valuesr variable variables visitor'sE what\ whichL window withB withint without written action{ adderror addrE backU begnum breakse checked clientE client addrE client client passwordG client typeH client usernameI commentt concatenate contentJ content typeJ cookie count countfields database database nameM nameN names namesO decodeP decode delete deletereply detailS detail linkS doscriptT conjunction doscript create button@ doscript post@ result@ value doscript postT doscript backU doscript doscript backW doscript presortX doscript presort backY duplicate duplicatereply emailbcc emailcc emailformat emailfrom emailhost emailsubject emailto encodee encode breakse encode htmlf encode encode smarth encode endnum errorstringl eventk event errorstringl event eventk event resultm event resultcoden extract field field namep findall findposition formr paramr getfield headers header headers htmlf comment commentt image include inliney inline inliney inline resultz insert lasso{ lasso action{ lasso process| lassopassword lassousername names names layout layout length linkS value logicalop logicalop value count lowercase math-add math-div math-mod math-mult math-round math-sub maxrecords maxrecords value nameM namesO nfound noresults nothing nshown opbegin opend operator option order paramr passwordG portal portal portal postT inline presortX process| random recid recid value record record record records referrer referrer referrer referrer remove removeleading removetrailing repeat repeat value repeating repeating repeating repetition replace reqfieldmissing required response response resultm resultcoden scripts search search search search field search search value selected server server server server cookie skiprecords skiprecords value smarth field order sortfield sortorder string string concatenate string countfields string extract string findposition string getfield string insert string length string lowercase string remove string removeleading string removetrailing string replace string uppercase timeout token token value total total records typeH update uppercase usernameI value value value value while while while CLOSE TAG COMMENT DESCRIPTION DISPLAY DESCRIPTION OPEN TAG PARAMETER SAMPLE HTML SYNTAX TAG NAME TAG TYPE Tag NameB Tag TypeB Open TagB A Close TagB DescriptionB CommentB SyntaxB (" ... " & ... A parameterB tempB Sample HTMLB Display DescriptionB Sunday Monday Tuesday Wednesday Thursday Friday Saturday January February March April August September October November December 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 12/11/97 Detail View A List View @@A Find View Detail ViewB A List ViewB ABAD>> ABAB>>Y << ABAM>>Z << ABAK>> $A List View Previous LDML 2.5 Reference v1 A Find ViewB H blueworldU [Tag]V [Name]^ [Type]e LDML 2.5 Reference v1 Add RecordC ActionD The -add action adds a record to the specified FileMaker Pro database. The sample syntax shows how to submit an request with a button on an HTML form. Selecting the button will instruct Lasso to process the data entered into the form and add a new record to the FileMaker Pro database. The name of the submit button must be -add and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src=" Tag Named Tag Typej Full Descriptionk Findl Cancelm Clear 3A List View LDML 2.5 Reference v1 Add Error ReplyC CommandD -adderror -adderror tag is used to specify a custom error page to be displayed when a problem is encountered with adding a record. If a file is not specified, Lasso will use a generic, default error page. The default error message reads as follows: Record created, There were errors with one or more of the fields. Possible errors include, but are not limited to: - an existing value was provided for a field that requires a unique value - a value was provided for a field that is auto- entered - a value was provided for a lookup field but the file containing the lookup values was not found - a value was entered that did not match any entries for a value list - any number of other errors about which FileMaker Pro will not be more specific. Note that when an add error occurs that a blank record will be added to the FileMaker Pro database, even though the action was not completed. searchgraphic.gif name="-add"> The name parameter must specify the action, even if the action is specified elsewhere. As another option, you could specify the action by combining it with the form action and other elements of the form. Using this method, the form action would begin as: <form action="action.lasso?-add&-database=Employees&-layout=summary& " method="post"> rest of the HTML form </form> The add action can also be part of a URL link as follows: <a href="Lasso.a cgi?-database=project%20database&-layout=main%20layout&-response=Add_Reply.html&fieldname=[field:"fieldname",url]&fieldname2=[field:"fieldname2",url]&-add">Add</A> Be sure to encode any spaces in the URL with a plus sign and to use the parameter with any FileMaker Pro database fields so the returned data is encoded for use on a URL, i.e., [field:"fieldname",url]. J7Adds a record to the specified FileMaker Pro database. L -addO P4<input type="submit" name="-add" value="Add Record"> <input type="submit" name="-add" value="Add Record"> The -add action adds a record to the specified FileMaker Pro database. The sample syntax shows how to submit an request with a button on an HTML form. Selecting the button will instruct Lasso to process the data entered into the form and add a new record to the FileMaker Pro database. The name of the submit button must be -add and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-add"> The name parameter must specify the action, even if the action is specified elsewhere. As another option, you could specify the action by combining it with the form action and other elements of the form. Using this method, the form action would begin as: <form action="action.lasso?-add&-database=Employees&-layout=summary& " method="post"> rest of the HTML form </form> The add action can al so be part of a URL link as follows: <a href="Lasso.acgi?-database=project%20database&-layout=main%20layout&-response=Add_Reply.html&fieldname=[field:"fieldname",url]&fieldname2=[field:"fieldname2",url]&-add">Add</A> Be sure to encode any spaces in the URL with a plus sign and to use the parameter with any FileMaker Pro database fields so the returned data is encoded for use on a URL, i.e., [field:"fieldname",url]. adderror begnum checked client client client password client client username content cookie database database names decode delete deletereply detail doscript doscript doscript doscript doscript presort doscript presort duplicate duplicatereply emailbcc emailcc emailformat emailfrom emailhost emailsubject emailto encode breaks encode encode encode smart encode endnum event event errorstring event result event resultcode field field findall param header comment image include inline inline result lasso action lasso process lassopassword lassousername names layout layout value logicalop logicalop value count JMDelivers the specified file if a problem is encountered with adding a record.L -adderrorO -Error (plus a workaround)PG<input type="hidden" name="-adderror" value="Pathto/YourFileName.html"> <input type="hidden" name="-adderror" value="Pathto/YourFileName.html"> -adderror tag is used to specify a custom error page to be displayed when a problem is encountered with adding a record. If a file is not specified, Lasso will use a generic, default error page. The default error message reads as follows: Record created, There were errors with one or more of the fields. Possible errors include, but are not limited to: - an existing value was provided for a field that r equires a unique value - a value was provided for a field that is auto-entered - a value was provided for a lookup field but the file containing the lookup values was not found - a value was entered that did not match any entries for a value list - any number of other errors about which FileMaker Pro will not be more specific. Note that when an add error occurs that a blank record will be added to the FileMaker Pro database, even though the action was not completed. Beginning NumberC SubstitutionD [begnum] The substitution tag [begNum] is used when displaying the numeric range of a found set of records. The [begNum] value is the number of the first record in the order. If there is only one group of records, or all records are returned in the same group, then the value of [begNum] is 1. J6Displays the numeric range of a found set of records. L [begnum]O [FMP-RangeStart]P [begnum] &[begnum] The substitution tag [begNum] is used when displaying the numeric range of a found set of records. The [begNum] value is the number of the first record in the order. If there is only one group of records, or all records are returned in the same group, then the value of [begNum] is 1. CheckedC Sub-ContainerD [checked] The [checked] tag instructs Lasso to place the checked parameter into the HTML element for the items selected in the database. It can be used only within the [value_list: [/value_list] container. It is most relevant when used with radio buttons and checkboxes. The [checked] tag simply returns the text checked if an item on a value list has been selected. The item must be part of the value list associated with the field specified by the [value_list: ] tag. It is useful when used ewithin a conditional statement to determine if a value list item is currently checked for a specific record in the database, since checked will appear if that item is a value in that field. Within conditional statements, the [checked] and [selected] tags are interchangeable and produce the same result. For more details, refer to the [value_list: ] tag. JwPlaces the "checked" parameter into the HTML element for the items specified using the [value_list:...] container tag. L [checked]N>Only valid within the [value_list:...] [/value_list] containerO [FMP-ValueListChecked]P [value_list:"YourFieldName"] <input type="checkbox" name="YourFieldName" value="[list_value]"[checked]> [list_value]<br> [/value_list] <input type="hidden" name="YourFieldName" value=""> [value_list:"YourFieldName"] <input type="checkbox" name="YourFieldName" value="[list_value]"[checked]> [list_value]<br> [/value_list] <input type="hidden" name="YourFieldName" value=""> The [checked] tag instructs Lasso to place the checked parameter into the HTML element for the items selected in the database. It can be used only within the [value_list: [/value_list] container. It is most relevant when used with radio buttons and checkboxes. The [checked] tag simply returns the text checked if an item on a value list has been selected. The item must be part of the value list associated with the field specified by the [value_list: ] tag. It is useful when used within a conditional statement to determine if a value list item is currently checked for a specific record in the database, since checked will appear if that item is a value in that field. Within conditional statements, the [checked] and [selected] tags are interchangeable and produce the same res C8ult. For more details, refer to the [value_list: ] tag. Client Domain AddressC SubstitutionD [client_addr] The [client_addr] tag is substituted with the visitor s domain name address. It is only available if domain name lookups are enabled in the Web server. If it is not, the client s IP address will be used. This information is taken from the visitor s Web browser settings. J#Displays the visitor's domain name.L [client_addr]N Accepts encoding parameters.O [FMP-ClientAddress]P [client_addr] [client_addr] The [client_addr] tag is substituted with the visitor s domain name address. It is only available if domain name lookups are enabled in the Web server. If it is not, the client s IP address will be used. This information is taken from the visitor s Web browser settings. Client IP AddressC SubstitutionD [client_ip] The [client_ip] tag inserts the client s IP address into the output HTML. This information is taken from settings entered into the visitor s Web browser.J!Displays the client's IP address.L [client_ip]N Accepts encoding parameters.O [FMP-ClientIP]P [client_ip]Q [client_ip] The [client_ip] tag inserts the client s IP address into the output HTML. This information is taken from settings entered into the visitor s Web browser. Client PasswordC SubstitutionD [client_password]I#Refer to the [client_username] tag.J Displays the current password.L [client_password]N Accepts encoding parameters.O [FMP-ClientPassword]P [client_password]Q6[client_password] Refer to the [client_username] tag. Client Browser TypeC SubstitutionD [client_type] The [client_type] tag inserts the type of browser the visitor is using into the output HTML. [client_type] is also known as the user agent and is sent by the browser in the HTTP request header. In theory, client type can be used to determine what sort of browser the person accessing your Web site is using. In practice, Netscape Navigator 3.0 may report Mozilla/3.0 (Macintosh; I; PPC) while Microsoft Internet Explorer 2.1 will report Mozilla/2.0 (compatible; MSIE 2.1; Mac_PowerPC) so BKit may not be possible to actually pinpoint the type of browser being used. J%Displays the visitor's browser type. L [client_type]N Accepts encoding parameters.O [FMP-ClientType]P [client_type] [client_type] The [client_type] tag inserts the type of browser the visitor is using into the output HTML. [client_type] is also known as the user agent and is sent by the browser in the HTTP request header. In theory, client type can be used to determine what sort of browser the person accessing your Web site is using. In practice, Netscape Navigator 3.0 may report Mozilla/3.0 (Macintosh; I; PPC) while Microsoft Internet Explorer 2.1 will report Mozilla/2.0 (compatible; MSIE 2.1; MaBZc_PowerPC) so it may not be possible to actually pinpoint the type of browser being used. Client UsernameC SubstitutionD [client_username] The [client_username] tag inserts the current user name into the output HTML. The value of [client_username] is the user name entered into the HTTP basic authentication dialog. With Lasso security, a user is prompted when first accessing a Lasso-served database. With realm-based security, a user first attempts to access a format file in a protected realm. If security is not checked then the value is not available. The password is also available using the [client_password] substitution tagB Displays the current username. L [client_username]N Accepts encoding parameters.O [FMP-ClientUserName]P#[client_username] [client_password] [client_username] [client_password] The [client_username] tag inserts the current user name into the output HTML. The value of [client_username] is the user name entered into the HTTP basic authentication dialog. With Lasso security, a user is prompted when first accessing a Lasso-served database. With realm-based security, a user first attempts to access a format file in a protected realm. If security is not checked then the value is not available. The password is also available using tB&he [client_password] substitution tag. Content TypeC SubstitutionD [content_type: ...] content_type substitution tag allows user to override default content type of text/html. The [content_type] tag must appear at the top and be the first item in the format file. If it is not, it is ignored by Lasso. Here s an example of use of this tag: [content_type: text/sgml"] The [content_type] tag is also ignored if it appears within a format file that is included in another format file via the [include] tag. J;Allows one to override default content type of "text/html."L [content_type: ...]N'The file type to use (i.e. text/sgml])O [FMP-ContentMimeType: ...]P [content_type: "MIME/Type"] [content_type: "MIME/Type"] content_type substitution tag allows user to override default content type of text/html. The [content_type] tag must appear at the top and be the first item in the format file. If it is not, it is ignored by Lasso. Here s an example of use of this tag: [content_type: text/sgml"] The [content_type] tag is also ignored if it appears within a format file that is included in another format file via the [include] tag. Display CookieC SubstitutionD [cookie: ...] After a cookie value has been set in a browser, the [cookie: ] tag can be used to retrieve the current value of a specific cookie. The name of the cookie is the same name as was specified by the [set_cookie] tag. The cookie value can only be retrieved if the path and domain name are the same as when the cookie was set. A space after the colon is optional, as are quotes around the name of the cookie. If problems are encountered with the display of a cookie, check that the path to the cooki e is the same as the path you are currently using to display the cookie. Cookies may be used in conditional [if] tags within Lasso format files. For example: [if: cookie:"siteid == field:"user"] HTML if condition is true [else] HTML if condition is false [/if] As shown, quotes are not used to surround the cookie tag, however quotes can (optionally) be used around the name of the cookie. The [cookie: ] tag accepts the optional encoding parameters. For example, the Qameter to URL-encode the cookie value: [cookie: siteid",url] If you do not want the cookie to be HTML encoded within the above conditional statement, the parameter can be used as follows: [if: (cookie:"siteid",raw) == field:"user"] Note that parenthesis were used to clarify the use of the raw parameter with the cookie tag. J@Displays the value of an existing cookie in a Lasso format file.L [cookie: ...]N Accepts encoding parameters.O [FMP-Cookie: ...]P [cookie: YourCookieName] [cookie: YourCookieName] After a cookie value has been set in a browser, the [cookie: ] tag can be used to retrieve the current value of a specific cookie. The name of the cookie is the same name as was specified by the [set_cookie] tag. The cookie value can only be retrieved if the path and domain name are the same as when the cookie was set. A space after the colon is optional, as are quotes around the name of the cookie. If problems are encountered with the display of a cookie, check that the path to the cookie is the same as the path you are currently using to display the cookie. Cookies may be used in conditional [if] tags within Lasso format files. For example: [if: cookie:"siteid == field:"user"] HTML if condition is true [else] HTML if condition is false [/if] As shown, quotes are not used to surround the cookie tag, however quotes can (optionally) be used around the name of the cookie. The [cookie: ] tag accepts the optional encoding parameters. kFor example, the parameter to URL-encode the cookie value: [cookie: siteid",url] If you do not want the cookie to be HTML encoded within the above conditional statement, the parameter can be used as follows: [if: (cookie:"siteid",raw) == field:"user"] Note that parenthesis were used to clarify the use of the raw parameter with the cookie tag. Specify DatabaseC CommandD -database The -database tag specifies which FileMaker Pro database Lasso should perform the action on. Only one database can be specified for an action. The name is not case-sensitive. To avoid confusion, do not give your database and layout the same name. Also, do not use ampersands, slashes, or other extended characters in database, layout, or field names, or field values. All other special characters should be encoded. This tag is required on any format files that reference FileMaker Pro databaseB fields. JJSpecifies on which FileMaker Pro database Lasso should perform an action. L -databaseO -DBP9<input type="hidden" name="-database" value="YourDBName"> <input type="hidden" name="-database" value="YourDBName"> The -database tag specifies which FileMaker Pro database Lasso should perform the action on. Only one database can be specified for an action. The name is not case-sensitive. To avoid confusion, do not give your database and layout the same name. Also, do not use ampersands, slashes, or other extended characters in database, layout, or field names, or field values. All other special characters should be encoded. This tag is requireBDd on any format files that reference FileMaker Pro database fields. Display Database NameC SubstitutionD [database_name] As Lasso processes a response format file, the [database_name] tag will be substituted for the name of the database that was referenced. This value can be used only on a form that was generated via Lasso (post-Lasso) and is determined by the database specified on the previous action. The value could simply be displayed, or entered into a field, for example a log database that records Lasso activity. Or, it could be used in a conditional statement to determine the HTML output. The sample s ayntax shows how to use the [database_name] tag to create a link to the same record, based on the database and layout name. This can be used on a post-Lasso file for a specific record (for example, within the [record][/record] tag container). Change the response to a file you want to switch to and the same record will be displayed using the new layout. J-Displays the name of the specified database. L [database_name]N Accepts encoding parameters.O [FMP-CurrentDatabase] <a href="action.lasso?-search&-database=database_name&-layout=layout_name&-response=YourFileName&-recid=recid_value"> Link to Same Record </a> <a href="action.lasso?-search&-database=database_name&-layout=layout_name&-response=YourFileName&-recid=recid_value"> Link to Same Record </a> As Lasso processes a response format file, the [database_name] tag will be substituted for the name of the database that was referenced. This value can be used only on a form that was generated via Lasso (post-Lasso) and is determined by the database specified on the previous action. The value could simply be displayed, or entered into a field, for example a log database that records Lasso activity. Or, it could be used in a conditional statement to determine the HTML output. The sample syntax shows how to use the [database_name] tag to create a link to the same record, based on the database and layout name. This can be used on a post-Lasso file for a specific record (for example, within the [record][/record] tag container). Change the response to a file you want to switch to and the same record will be displayed using the new layoC Display Open DatabaseC Sub-ContainerD [db_name] <The [db_name] tag can only used within the [db_names] [/db_names] container tags to display the names of a currently open database. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. J/Displays the name of a currently open database.L [db_name]N&Is a tag in the Database_Info_Tags.mod (internal to web companion)P&[db_names] [db_name]<br> [/db_names] d[db_names] [db_name]<br> [/db_names] The [db_name] tag can only used within the [db_names] [/db_names] container tags to display the names of a currently open database. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. Display All Open DatabasesC ContainerD [db_names]E [/db_names] The [db_names] tag can be used to retrieve the names of all currently open databases. The [db_name] tag will be substituted for the database names. The [db_name] tag can be used only within the [db_names: [/db_names] container tags. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. J3Displays the names of all currently open databases. [db_names] ... [/db_names]NXWithin container: the [db_name] substitution tag. Is a tag in the Database_Info_Tags.modO (internal to web companion)P&[db_names] [db_name]<br> [/db_names] [db_names] [db_name]<br> [/db_names] The [db_names] tag can be used to retrieve the names of all currently open databases. The [db_name] tag will be substituted for the database names. The [db_name] tag can be used only within the [db_names: [/db_names] container tags. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. Decode URLC SubstitutionD [decode_url: ...] The [decode_url: ] substitution tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. This tag will concatenate all specified text together and remove any encoding from the text string. In other words, this tag can be used to undo what the [encode_url: ] tag does. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surrounded by quotes and sepB arated by commas. Example: [decode_url: This%20is%20%3cb%3eth%e9%20string%3c%2fb%3e%d] This example would output to: This is <b>th string</b> JOConcatenates all specified text and removes any encoding from the text string.L [decode_url: ...]N multiple unnamed parametersP [decode_url: "sometext"] [decode_url: "sometext"] The [decode_url: ] substitution tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. This tag will concatenate all specified text together and remove any encoding from the text string. In other words, this tag can be used to undo what the [encode_url: ] tag does. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is sB urrounded by quotes and separated by commas. Example: [decode_url: This%20is%20%3cb%3eth%e9%20string%3c%2fb%3e%d] This example would output to: This is <b>th string</b> Delete RecordC ActionD -delete The -delete action deletes a specific record in the specified FileMaker Pro database. The sample syntax shows how to submit a delete request with a button on an HTML form. Lasso will delete the currently displayed record when the submit button is selected. The -delete action can only be used on a post-Lasso form since Lasso needs to first identify which record is to be deleted (by retrieving the record ID for a specific record after a Lasso action). Also, records can only be deleted one at a time, it is not possible to delete a group of records listed on a hitlist. In order for a delete action to be performed, the -recid tag must specify the record ID of the record to be deleted. The syntax used to direct the action to a specific record is as follows: <input type="hidden name="-recid value="[recid_value]"> The name of the submit button must be -delete and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the f >ollowing example: <input type="Image src="searchgraphic.gif name="-delete"> The name parameter must specify the action, even if the action is specified elsewhere. A JavaScript can be used to present a dialog that prompts the user to confirm the delete request and to provide an opportunity to cancel the delete. J*Deletes a specific record from a database.L -deleteO -DeleteP:<input type="submit" name="-delete" value="Delete Record"> <input type="submit" name="-delete" value="Delete Record"> The -delete action deletes a specific record in the specified FileMaker Pro database. The sample syntax shows how to submit a delete request with a button on an HTML form. Lasso will delete the currently displayed record when the submit button is selected. The -delete action can only be used on a post-Lasso form since Lasso needs to first identify which record is to be deleted (by retrieving the record ID for a specific record a fter a Lasso action). Also, records can only be deleted one at a time, it is not possible to delete a group of records listed on a hitlist. In order for a delete action to be performed, the -recid tag must specify the record ID of the record to be deleted. The syntax used to direct the action to a specific record is as follows: <input type="hidden name="-recid value="[recid_value]"> The name of the submit button must be -delete and the value is any text you want to appear on the bu ztton. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-delete"> The name parameter must specify the action, even if the action is specified elsewhere. A JavaScript can be used to present a dialog that prompts the user to confirm the delete request and to provide an opportunity to cancel the delete. Delete ReplyC CommandD -deletereply The -deleteReply tag indicates which reply format file to use after a successful delete action. A delete reply file is required if a record is deleted using the -delete action tag.JHSpecifies the reply format file to use after a successful delete action.L -deletereplyO -Error (plus a workaround)PJ<input type="hidden" name="-deletereply" value="Pathto/YourFileName.html"> <input type="hidden" name="-deletereply" value="Pathto/YourFileName.html"> The -deleteReply tag indicates which reply format file to use after a successful delete action. A delete reply file is required if a record is deleted using the -delete action tag. Detail LinkC SubstitutionD [detail_link: ...] The [detail_link: ] tag creates a link to a specific record in a FileMaker Pro database. The link created is generally from one specific record to a detail view of that record. It is typically used on a hitlist format file. A hitlist is a list of the current set of found records. The [detail_link: ] should be placed within [record] [/record] container tags or on a file that would only contain a single record (i.e., an add or update reply). The response and layout must be specified with in the [detail_link: ] tag. The database name does not need to be specified since the link will only work with the database that was used to call up the format file that the [detail_link: ] tag is on. Names with spaces or special characters do not need to be encoded, as Lasso will URL encode the elements of the link automatically. If encoded values are included, the Lasso will simply include them in the final link. In other words you could specify a response file named Detail Format.htm as either: <a href="[detail_link:layout="main",response="Detail Format.html"]"> [field:"YourFieldName"]</a> <a href="[detail_link:layout="main",response="Detail%20Format.html"]">Link</a> However, make sure that the spaces between the name value pairs are NOT encoded, for example, do not use: <a href="[detail_link:%20layout="main",%20response="Detail%20Format.html"]">Link</a> If a token was established on the previous page that called up the page the detail link is on, then the token will be included automatically with the [detail_link: ] string. It is also possible to add a token with the detail link. The following shows how to add a new token to a detail link: <a href="[detail_link:layout="summary",response="FileName.html"]&-token=yourtokenname"> [field:"YourFieldName"]</a> However, keep in mind that if a token was set on the previous page this token will override the previously set token. When this link is created, Lasso will insert the value of the reco rd ID for the current record in place of the [recid_value] tag. If you view the source of the hitlist file you will be able to see how Lasso formats this tag to automatically create an embedded search to a specific record. The URL link is in the format: <a href="Lasso.acgi?-database=employees&-layout=main&-response=detail.html& -recid=[recid_value]&-search">Link </A> The detail link reference can also be manually constructed and used on any file returned by Lasso to link to a specific reF`cord. Note: The [detail_link: ] tag was specified in previous versions of Lasso as [recid: J3Creates a link to a specific record in a database. L [detail_link: ...]N4Name of a layout and the response file path and nameO [FMP-LinkRecID: ...]Ph<a href="[detail_link:layout="detail",response="Pathto/YourFileName.html"]"> [field:"YourFieldName"]</a> <a href="[detail_link:layout="detail",response="Pathto/YourFileName.html"]"> [field:"YourFieldName"]</a> The [detail_link: ] tag creates a link to a specific record in a FileMaker Pro database. The link created is generally from one specific record to a detail view of that record. It is typically used on a hitlist format file. A hitlist is a list of the current set of found records. The [detail_link: ] should be placed within [record] [/record] container tags or on a file that would on ly contain a single record (i.e., an add or update reply). The response and layout must be specified within the [detail_link: ] tag. The database name does not need to be specified since the link will only work with the database that was used to call up the format file that the [detail_link: ] tag is on. Names with spaces or special characters do not need to be encoded, as Lasso will URL encode the elements of the link automatically. If encoded values are included, the Lasso will simply include them in the final link. In other words you could specify a response file named Detail Format.html as either: <a href="[detail_link:layout="main",response="Detail Format.html"]"> [field:"YourFieldName"]</a> <a href="[detail_link:layout="main",response="Detail%20Format.html"]">Link</a> However, make sure that the spaces between the name value pairs are NOT encoded, for example, do not use: <a href="[detail_link:%20layout="main",%20response="Detail%20Format.html"]">Link</a If a token was established on the previous page that called up the page the detail link is on, then the token will be included automatically with the [detail_link: ] string. It is also possible to add a token with the detail link. The following shows how to add a new token to a detail link: <a href="[detail_link:layout="summary",response="FileName.html"]&-token=yourtokenname"> [field:"YourFieldName"]</a> However, keep in mind that if a token was set on the previous page this token w ill override the previously set token. When this link is created, Lasso will insert the value of the record ID for the current record in place of the [recid_value] tag. If you view the source of the hitlist file you will be able to see how Lasso formats this tag to automatically create an embedded search to a specific record. The URL link is in the format: <a href="Lasso.acgi?-database=employees&-layout=main&-response=detail.html& -recid=[recid_value]&-search">Link </A> The detail link F reference can also be manually constructed and used on any file returned by Lasso to link to a specific record. Note: The [detail_link: ] tag was specified in previous versions of Lasso as [recid: FMP Script Post-LassoC CommandD -doscript.post FileMaker Pro scripts can be run in forms by themselves or in conjunction with a Lasso action (can be add, search, update, delete, etc.). The -doscript tags are used to indicate which script to run when a Lasso action occurs. Scripts can be executed before and after the action is taken and before the records are sorted (for search actions) using optional parameters. The doscript tags include: doscript.pre doscript.presort doscript.post doscript.pre.back doscript.post.back doscript.preso rt.back If the tag is specified as -doscript, the default -doscript.post tag is assumed. Each is indicated with a period after -doscript, and then the parameter with no spaces. (Note: Prior to Lasso 2.5, a comma was used to separate -doscript from the parameter name. This syntax is no longer supported.) The user can specify as many scripts as they want. The -doscript tags takes the following syntax: <input type="hidden name="-doscript.post value="YourScriptName"> You will need a hid den input for each script you want to run when a Lasso action is taken. The -scripts action is used in conjunction with the -doscript tag to create a button that will execute a script as a single action. The various -doscript tags and -scripts action tags can also be embedded in a URL. In addition, with Lasso 2.5 you can specify that the FileMaker Pro application not be brought to the front while a script is being executed. These parameters should only be used if the script is very simple and can be executed without requiring FileMaker Pro as the frontmost application. Otherwise, if a script sorts a large set of records it could put a drain on the ability of FileMaker Pro to execute the script. While the script is running no other access to the database is possible and so it is unavailable to any other database activity. If you don t want it to run on certain occasions, or want to select between different scripts, create a pop-up (or checkbox) to specify the script, e.g.: Select script to run when the update is submitted: <select name="-doscript.post size=1> <option value=" selected>None <option value="script1">Run Script 1 to do something <option value="script2">Run Script 2 to do something <option value="script3">Run Script 3 to do something </select> J,Specifies the FileMaker Pro script to run. L -doscript.postNGParameters: pre, presort, post, back, pre.back, post.back, presort.backO -ScriptPB<input type="hidden" name="-doscript.post" value="YourScriptName"> <input type="hidden" name="-doscript.post" value="YourScriptName"> FileMaker Pro scripts can be run in forms by themselves or in conjunction with a Lasso action (can be add, search, update, delete, etc.). The -doscript tags are used to indicate which script to run when a Lasso action occurs. Scripts can be executed before and after the action is taken and before the records are sorted (for search actions) using optional parameters. The doscript tags include: doscript.pre doscript.preso doscript.post doscript.pre.back doscript.post.back doscript.presort.back If the tag is specified as -doscript, the default -doscript.post tag is assumed. Each is indicated with a period after -doscript, and then the parameter with no spaces. (Note: Prior to Lasso 2.5, a comma was used to separate -doscript from the parameter name. This syntax is no longer supported.) The user can specify as many scripts as they want. The -doscript tags takes the following syntax: <input type="hidden name="-doscript.post value="YourScriptName"> You will need a hidden input for each script you want to run when a Lasso action is taken. The -scripts action is used in conjunction with the -doscript tag to create a button that will execute a script as a single action. The various -doscript tags and -scripts action tags can also be embedded in a URL. In addition, with Lasso 2.5 you can specify that the FileMaker Pro application not be brought to the front while a script is being execute d. These parameters should only be used if the script is very simple and can be executed without requiring FileMaker Pro as the frontmost application. Otherwise, if a script sorts a large set of records it could put a drain on the ability of FileMaker Pro to execute the script. While the script is running no other access to the database is possible and so it is unavailable to any other database activity. If you don t want it to run on certain occasions, or want to select between different k scripts, create a pop-up (or checkbox) to specify the script, e.g.: Select script to run when the update is submitted: <select name="-doscript.post size=1> <option value=" selected>None <option value="script1">Run Script 1 to do something <option value="script2">Run Script 2 to do something <option value="script3">Run Script 3 to do something </select> A#FMP Script Post-Lasso in BackgroundC CommandD -doscript.post.backI Processes script after all other specified Lasso actions are completed. Keeps FileMaker Pro in the background while processing. Refer to the -doscript.post tag for more details.J-Specifies the FileMaker Pro script to run. L -doscript.post.backNGParameters: pre, presort, post, back, pre.back, post.back, presort.backO (not needed)PG<input type="hidden" name="-doscript.post.back" value="YourScriptName"> <input type="hidden" name="-doscript.post.back" value="YourScriptName"> Processes script after all other specified Lasso actions are completed. Keeps FileMaker Pro in the background while processing. Refer to the -doscript.post tag for more details. FMP Script Pre-LassoC CommandD -doscript.preI Processes script before all other specified Lasso actions. Brings FileMaker Pro to the foreground while processing then to background after completion. Refer to the -doscript.post tag for more details.J-Specifies the FileMaker Pro script to run. L -doscript.preNGParameters: pre, presort, post, back, pre.back, post.back, presort.backO -Script.PrefindPA<input type="hidden" name="-doscript.pre" value="YourScriptName"> <input type="hidden" name="-doscript.pre" value="YourScriptName"> Processes script before all other specified Lasso actions. Brings FileMaker Pro to the foreground while processing then to background after completion. Refer to the -doscript.post tag for more details. A"FMP Script Pre-Lasso in BackgroundC CommandD -doscript.pre.backI Processes script before all other specified Lasso actions. Keeps FileMaker Pro in the background while processing. Keeps FileMaker Pro in the background while processing. Refer to the -doscript.post tag for more details.J-Specifies the FileMaker Pro script to run. L -doscript.pre.backNGParameters: pre, presort, post, back, pre.back, post.back, presort.backO (not needed)PF<input type="hidden" name="-doscript.pre.back" value="YourScriptName"> $<input type="hidden" name="-doscript.pre.back" value="YourScriptName"> Processes script before all other specified Lasso actions. Keeps FileMaker Pro in the background while processing. Keeps FileMaker Pro in the background while processing. Refer to the -doscript.post tag for more details. FMP Script Pre-SortC CommandD -doscript.presort Processes script before Lasso -sort command is invoked in a Lasso -search action. Only works in conjunction with Lasso -search action. Brings FileMaker Pro in the foreground while processing then to background after completion. Refer to the -doscript.post tag for more details. J-Specifies the FileMaker Pro script to run. L -doscript.presortNGParameters: pre, presort, post, back, pre.back, post.back, presort.backO -Script.PresortPE<input type="hidden" name="-doscript.presort" value="YourScriptName"> \<input type="hidden" name="-doscript.presort" value="YourScriptName"> Processes script before Lasso -sort command is invoked in a Lasso -search action. Only works in conjunction with Lasso -search action. Brings FileMaker Pro in the foreground while processing then to background after completion. Refer to the -doscript.post tag for more details. A!FMP Script Pre-Sort in BackgroundC CommandD -doscript.presort.back Processes script before Lasso -sort command is invoked in a Lasso -search action. Only works in conjunction with Lasso -search action. Refer to the -doscript.post tag for more details. Keeps FileMaker Pro in the background while processing.J-Specifies the FileMaker Pro script to run. L -doscript.presort.backNGParameters: pre, presort, post, back, pre.back, post.back, presort.backO (not needed)PJ<input type="hidden" name="-doscript.presort.back" value="YourScriptName"> <<input type="hidden" name="-doscript.presort.back" value="YourScriptName"> Processes script before Lasso -sort command is invoked in a Lasso -search action. Only works in conjunction with Lasso -search action. Refer to the -doscript.post tag for more details. Keeps FileMaker Pro in the background while processing. Duplicate RecordC ActionD -duplicate A single record in a FileMaker Pro database can be duplicated using the -duplicate action. The sample syntax shows how to submit a duplicate request with a button on an HTML form. The currrently displayed record will be duplicated when the button is selected. The new record is displayed using the format file specified by the -response tag. The -duplicate action can be used only on a post-Lasso form since Lasso needs to first identify which record is to be updated (by retrieving the reco rd ID for a specific record after a Lasso action). Thus, the record ID must also be specified on the format file as follows: <input type="hidden name="-recid value="[recid_value]"> The name of the submit button must be -duplicate and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-duplicate"> Security Note: In order to execute the -duplicate action, the c urrent user must have permission for the database. If the user does not, a database security violation error is returned. Duplicates a record.L -duplicateO -DupPE<input type="submit" name="-duplicate" value="Duplicate this Record"> <input type="submit" name="-duplicate" value="Duplicate this Record"> A single record in a FileMaker Pro database can be duplicated using the -duplicate action. The sample syntax shows how to submit a duplicate request with a button on an HTML form. The currrently displayed record will be duplicated when the button is selected. The new record is displayed using the format file specified by the -response tag. The -duplicate action can be used only on a post-Lasso form since Lasso needs to first identify which record is to be updated (by retrieving the record ID for a specific record after a Lasso action). Thus, the record ID must also be specified on the format file as follows: <input type="hidden name="-recid value="[recid_value]"> The name of the submit button must be -duplicate and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-dupliC cate"> Security Note: In order to execute the -duplicate action, the current user must have permission for the database. If the user does not, a database security violation error is returned. Duplicate ReplyC CommandD -duplicatereplyI The -duplicatereply tag specifies the reply format file for a successful record duplication. Optionally, it can be used with the -duplicate action tag. If no file is specified, the file specified by the -response tag is used for the reply. JDSpecifies the reply format file for a successful record duplication.L -duplicatereplyO -response (plus a workaround)PM<input type="hidden" name="-duplicatereply" value="Pathto/YourFileName.html"> ><input type="hidden" name="-duplicatereply" value="Pathto/YourFileName.html"> The -duplicatereply tag specifies the reply format file for a successful record duplication. Optionally, it can be used with the -duplicate action tag. If no file is specified, the file specified by the -response tag is used for the reply. ElseC Sub-ContainerD [else]I The [else] tag is only valid within an [if: [/if] container. It can also appear as [else: if: ] for nested conditional statements. Refer to the [if: [/if] container tag for details.JlControls the conditions of what is displayed or included in a file as an option added to the [if:...] tag. L [else]N.Only valid within the [if:...] [/if] containerO [FMP-Else] [if: field: "YourFieldName" operator "value"] ...HTML if condition is true... [else] ...HTML if condition is false... [/if] A[if: field: "YourFieldName" operator "value"] ...HTML if condition is true... [else] ...HTML if condition is false... [/if] The [else] tag is only valid within an [if: [/if] container. It can also appear as [else: if: ] for nested conditional statements. Refer to the [if: [/if] container tag for details. Else IfC Sub-ContainerD [else: if: ...]I The [else:if: ] tag is only valid within an [if: [/if] container and is a variation on the [else] tag. Refer to the [if: [/if] container tag for details.JlControls the conditions of what is displayed or included in a file as an option added to the [if:...] tag. L [else: if: ...]N.Only valid within the [if:...] [/if] containerPb[if: condition] text or tags [else: if: condition] text or tags [else] text or tags [/if] [if: condition] text or tags [else: if: condition] text or tags [else] text or tags [/if] The [else:if: ] tag is only valid within an [if: [/if] container and is a variation on the [else] tag. Refer to the [if: [/if] container tag for details. A Email BCCC CommandD -emailbcc The -emailbcc tag is an optional tag that can be used with the email notification tags to send a carbon copy of an email message to the email address indicated. There are five required email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. If a valid emailbcc address is included the -emailto tag can be left out. In other words, the -emailbcc replaces the -emailto tag in that case. For more details on email notification, refer to the B Email Host tag. JOSends a "blind carbon copy" of an email message to the email address indicated.L -emailbccO -MailBCC PC<input type=hidden name="-emailbcc" value="BCCReceiver@Domain.com"> <input type=hidden name="-emailbcc" value="BCCReceiver@Domain.com"> The -emailbcc tag is an optional tag that can be used with the email notification tags to send a carbon copy of an email message to the email address indicated. There are five required email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. If a valid emailbcc address is included the -emailto tag can be left out. In other words, the -emailbcc replaces the -emailto taBVg in that case. For more details on email notification, refer to the Email Host tag. Email CCC CommandD -emailcc The -emailcc tag is an optional tag that can be used with the email notification tags to send a carbon copy of an email message to the email address indicated. There are five required email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. If a valid emailcc address is included the -emailto tag can be left out. In other words, the -emailcc replaces the -emailto tag in that case. For more details on email notification, refer to the ail Host tag. JISends a "carbon copy" of an email message to the email address indicated.L -emailccO -MailCCPA<input type=hidden name="-emailcc" value="CCReceiver@Domain.com"> <input type=hidden name="-emailcc" value="CCReceiver@Domain.com"> The -emailcc tag is an optional tag that can be used with the email notification tags to send a carbon copy of an email message to the email address indicated. There are five required email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. If a valid emailcc address is included the -emailto tag can be left out. In other words, the -emailcc replaces the -emailto tag in BQthat case. For more details on email notification, refer to the Email Host tag. Email FormatC CommandD -emailformatI The -emailformat tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. For more details on email notification, refer to the Email Host tag.JSIncluded in order for Lasso to send an email message after a Lasso action is taken.L -emailformatO -MailFormat PF<input type="hidden" name="-emailformat" value="Pathto/EmailFile.txt"> (<input type="hidden" name="-emailformat" value="Pathto/EmailFile.txt"> The -emailformat tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. For more details on email notification, refer to the Email Host tag. Email FromC CommandD -emailfromI The -emailfrom tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. For more details on email notification, refer to the Email Host tag.JSIncluded in order for Lasso to send an email message after a Lasso action is taken.L -emailfromO -MailFromPA<input type="hidden" name="-emailfrom" value="Sender@Domain.com"> !<input type="hidden" name="-emailfrom" value="Sender@Domain.com"> The -emailfrom tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. For more details on email notification, refer to the Email Host tag. Email HostC CommandD -emailhost Lasso has the ability to automatically send an email message after a Lasso action is taken. The five Lasso email tags can be included on ANY Lasso format file, embedded in a URL link, or used within an inline action. Whenever this file is passed through Lasso, or the hyperlink selected, the email commands that are contained therein are processed. If the email tags are on an add or update form, the data just entered can be included since the email action occurs after the action that initiat es the email. All five email command tags must be assigned a value or the message will not be sent. These include: -emailhost, -emailfrom, -emailsubject, -emailformat, and either one of the -emailto, -emailcc, or -emailbcc tags. The email message in either case is formatted according to the file specified with the -emailformat tag. There can be multiple destination addresses specified, but only one -emailhost, -emailfrom, -emailsubject, or -emailformat per Lasso action. The typical use of the email tags within an HTML form is shown in the sample syntax. There are two optional tags that can appear as: <input type=hidden name="-emailcc value="ccreceiver@ccreceiverdomain.com"> <input type=hidden name="-emailbcc value="bccreceiver@bccreceiverdomain.com"> Lasso can send email as long as at least one address is specified. An inline tag can be used to send an email message. In addition, email can be sent without any database activity using the followi ng syntax: [inline: nothing, emailhost="mail.domain.com", emailfrom="sender@senderdomain.com", emailto="receiver@receiver.com", emailsubject="Email Delivered by Lasso", emailformat="/login/Email_Format.txt"] The email format file should be specified relative to the current URL, in this case Email_Format.txt can be found within a folder named login that is located at the root level of the web serving folder. JSIncluded in order for Lasso to send an email message after a Lasso action is taken.L -emailhostO -MailHost \<input type="hidden" name="-emailhost" value="mail.senderdomain.com"> <input type="hidden" name="-emailfrom" value="sender@domain.com"> <input type="hidden" name="-emailto" value="receiver@domain.com"> <input type="hidden" name="-emailsubject" value="Email Delivered by Lasso"> <input type="hidden" name="-emailformat" value="Pathto/EmailFile.txt"> <input type="hidden" name="-emailhost" value="mail.senderdomain.com"> <input type="hidden" name="-emailfrom" value="sender@domain.com"> <input type="hidden" name="-emailto" value="receiver@domain.com"> <input type="hidden" name="-emailsubject" value="Email Delivered by Lasso"> <input type="hidden" name="-emailformat" value="Pathto/EmailFile.txt"> Lasso has the ability to automatically send an email message after a Lasso action is taken. The five Lasso email tags can be included on ANY Las so format file, embedded in a URL link, or used within an inline action. Whenever this file is passed through Lasso, or the hyperlink selected, the email commands that are contained therein are processed. If the email tags are on an add or update form, the data just entered can be included since the email action occurs after the action that initiates the email. All five email command tags must be assigned a value or the message will not be sent. These include: -emailhost, -emailfrom, -em ailsubject, -emailformat, and either one of the -emailto, -emailcc, or -emailbcc tags. The email message in either case is formatted according to the file specified with the -emailformat tag. There can be multiple destination addresses specified, but only one -emailhost, -emailfrom, -emailsubject, or -emailformat per Lasso action. The typical use of the email tags within an HTML form is shown in the sample syntax. There are two optional tags that can appear as: <input type=hidden name="- emailcc value="ccreceiver@ccreceiverdomain.com"> <input type=hidden name="-emailbcc value="bccreceiver@bccreceiverdomain.com"> Lasso can send email as long as at least one address is specified. An inline tag can be used to send an email message. In addition, email can be sent without any database activity using the following syntax: [inline: nothing, emailhost="mail.domain.com", emailfrom="sender@senderdomain.com", emailto="receiver@receiver.com", emailsubject="E mail Delivered by Lasso", emailformat="/login/Email_Format.txt"] The email format file should be specified relative to the current URL, in this case Email_Format.txt can be found within a folder named login that is located at the root level of the web serving folder. Email SubjectC CommandD -emailsubjectI The -emailsubject tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. For more details on email notification, refer to the Email Host tag.JSIncluded in order for Lasso to send an email message after a Lasso action is taken.L -emailsubjectO -MailSubPK<input type="hidden" name="-emailsubject" value="Email Delivered by Lasso"> .<input type="hidden" name="-emailsubject" value="Email Delivered by Lasso"> The -emailsubject tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. For more details on email notification, refer to the Email Host tag. Email ToC CommandD -emailto -The -emailto tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. However, it can be left out if either the -emailcc or -emailbcc tag is included. For more details on email notification, refer to the Email Host tag. JSIncluded in order for Lasso to send an email message after a Lasso action is taken.L -emailtoO -MailToPA<input type="hidden" name="-emailto" value="Receiver@Domain.com"> p<input type="hidden" name="-emailto" value="Receiver@Domain.com"> The -emailto tag is one of the five Lasso email tags that must be included in order for Lasso to send an email message after a Lasso action is taken. However, it can be left out if either the -emailcc or -emailbcc tag is included. For more details on email notification, refer to the Email Host tag. Encode BreaksC SubstitutionD [encode_breaks: ...] This tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. The [encode_breaks: ] substitution tag will concatenate all specified text together and then apply Lasso Breaks encoding. Breaks encoding will translate all carriage return characters into HTML <br> tags. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surrounded by quotes and sep arated by commas. Example: [encode_breaks: This is", <b>th string</b> 2 B encoded This example would output something similar to: This is <b>thé string</b><br> 2 B encoded JRConcatenates all specified text together and then applies Lasso "Breaks" encoding.L [encode_breaks: ...]N multiple unnamed parametersP [encode_breaks: "sometext"] [encode_breaks: "sometext"] This tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. The [encode_breaks: ] substitution tag will concatenate all specified text together and then apply Lasso Breaks encoding. Breaks encoding will translate all carriage return characters into HTML <br> tags. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter i s surrounded by quotes and separated by commas. Example: [encode_breaks: This is", <b>th string</b> 2 B encoded This example would output something similar to: This is <b>thé string</b><br> 2 B encoded Encode HTMLC SubstitutionD [encode_html: ...] This tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. The [encode_html: ] substitution tag will concatenate all specified text together and then HTML encode that text string. HTML encoding will translate all extended characters, including angle brackets, into their HTML entities. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surround ed by quotes and separated by commas. Example: [encode_html: This is", <b>th string</b> 2 B encoded This example would output: This is <b>thé string</b> 2 B encoded JHConcatenates all specified text and then HTML encodes that text string.L [encode_html: ...]N multiple unnamed parametersP [encode_html: "sometext"] [encode_html: "sometext"] This tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. The [encode_html: ] substitution tag will concatenate all specified text together and then HTML encode that text string. HTML encoding will translate all extended characters, including angle brackets, into their HTML entities. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags . Each parameter is surrounded by quotes and separated by commas. Example: [encode_html: This is", <b>th string</b> 2 B encoded This example would output: This is <b>thé string</b> 2 B encoded Encode RawC SubstitutionD [encode_raw: ...] This tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. The [encode_raw: ] substitution tag will concatenate all specified text together and then apply Lasso encoding. Raw encoding does not translate HTML entities, but will translate the Mac character set to ISO Latin-1. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surrounded byB quotes and separated by commas. Example: [encode_raw: This is", <b>th string</b>"] This example would output something similar to: This is <b>th string</b> 'JGConcatenates all specified text and then applies Lasso "Raw" encoding.L [encode_raw: ...]N multiple unnamed parametersP [encode_raw: "sometext"] [encode_raw: "sometext"] This tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. The [encode_raw: ] substitution tag will concatenate all specified text together and then apply Lasso encoding. Raw encoding does not translate HTML entities, but will translate the Mac character set to ISO Latin-1. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. EachB parameter is surrounded by quotes and separated by commas. Example: [encode_raw: This is", <b>th string</b>"] This example would output something similar to: This is <b>th string</b> Encode SmartC SubstitutionD [encode_smart: ...] The [encode_smart: ] substitution tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. This tag will concatenate all specified text together and then apply Lasso Smart encoding. Smart encoding will encode extended characters into their HTML entities, but will not convert angled brackets, allowing imbedded HTML to pass through. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surrounded by quotes and separated by commas. Example: [encode_smart: This is", <b>th string</b> 2 B encoded This example would output something similar to: This is <b>thé string</b> 2 B encoded JQConcatenates all specified text together and then applies Lasso "Smart" encoding.L [encode_smart: ...]N multiple unnamed parametersP [encode_smart: "sometext"] [encode_smart: "sometext"] The [encode_smart: ] substitution tag is part of the Encoding_Tags.mod module for text encoding of any text or values substituted into a Lasso-processed file. This tag will concatenate all specified text together and then apply Lasso Smart encoding. Smart encoding will encode extended characters into their HTML entities, but will not convert angled brackets, allowing imbedded HTML to pass through. The tag can contain multiple unnamed parameters such as l !iteral text elements or Lasso substitution tags. Each parameter is surrounded by quotes and separated by commas. Example: [encode_smart: This is", <b>th string</b> 2 B encoded This example would output something similar to: This is <b>thé string</b> 2 B encoded Encode URLC SubstitutionD [encode_url: ...] The [encode_url: ] substitution tag is part of the encoding tags module which provides text encoding utilities. These tags can be applied to any text or values substituted into a Lasso-processed file. In order for this tag to be used, the Encoding_Tags.mod module must be present in the Lasso Modules folder when Lasso is initially launched. This tag will concatenate all specified text together and then URL-encode that text string. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surrounded by quotes and separated by commas. Example: [encode_url: this is some text some more text"] This example syntax will output: this%20is%20some%20text%20some%20more%20text Lasso substitution tags can also be included, for example: [encode_url: http://", client_ip, field:file_path] This example would output something similar to: http%3a%2f%2f202.252.25.63employees%2fdetail.html )J9Concatenates all specified text and then URL encodes it.L [encode_url: ...]N multiple unnamed parametersP [encode_url: "sometext"] [encode_url: "sometext"] The [encode_url: ] substitution tag is part of the encoding tags module which provides text encoding utilities. These tags can be applied to any text or values substituted into a Lasso-processed file. In order for this tag to be used, the Encoding_Tags.mod module must be present in the Lasso Modules folder when Lasso is initially launched. This tag will concatenate all specified text together and then URL-encode that text string. The tag can contain multiple unnamed parameters such as literal text elements or Lasso substitution tags. Each parameter is surrounded by quotes and separated by commas. Example: [encode_url: this is some text some more text"] This example syntax will output: this%20is%20some%20text%20some%20more%20text Lasso substitution tags can also be included, for example: [encode_url: http://", client_ip, field:file_path] This example would output something similar to: http%3a%2f%2f202.252.25.63employees%2C fdetail.html Ending NumberC SubstitutionD [endnum] DThe substitution tag [endNum] is used when displaying the numeric range of a found set of records. The [endNum] value is the number of the last record in the order. If there is only one group of records, or all records are returned in the same group, then the value of [endNum] is the same as the number of records returned. J@Displays the ending number of a range of a found set of records.L [endnum]O [FMP-RangeEnd] [endnum] N[endnum] The substitution tag [endNum] is used when displaying the numeric range of a found set of records. The [endNum] value is the number of the last record in the order. If there is only one group of records, or all records are returned in the same group, then the value of [endNum] is the same as the number of records returned. Apple EventC ContainerD [event: ...]E [/event]I Apple_Event_Tag.mod must be installed for this tag to be available. The event tag is described in the Lasso User Guide. J Specifies an Apple Event.L [event: ...] ... [/event]N3class, id, target, wait_reply, and the event stringO-(accomplished via FM Pro ScriptMaker scripts)P`[event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] event_string [/event] [event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] event_string [/event] Apple_Event_Tag.mod must be installed for this tag to be available. The event tag is described in the Lasso User Guide. Event Error StringC Sub-ContainerD [event_errorstring]I Apple_Event_Tag.mod must be installed to use this command. This tag is valid only within the [event: [/event] container. The event tag is described in the Lasso User Guide. J7Specifies an error string returned from an Apple Event.L [event_errorstring]N3class, id, target, wait_reply, and the event stringPf[event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] [event_errorstring] [/event] [event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] [event_errorstring] [/event] Apple_Event_Tag.mod must be installed to use this command. This tag is valid only within the [event: [/event] container. The event tag is described in the Lasso User Guide. Event ResultC Sub-ContainerD [event_result]I Apple_Event_Tag.mod must be installed to use this command. This tag is valid only within the [event: [/event] container. The event tag is described in the Lasso User Guide. J'Specifies the result of an Apple Event.L [event_result]N3class, id, target, wait_reply, and the event stringPa[event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] [event_result] [/event] [event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] [event_result] [/event] Apple_Event_Tag.mod must be installed to use this command. This tag is valid only within the [event: [/event] container. The event tag is described in the Lasso User Guide. Event Result CodeC Sub-ContainerD [event_resultcode]I Apple_Event_Tag.mod must be installed to use this command. This tag is valid only within the [event: [/event] container. The event tag is described in the Lasso User Guide. .J,Specifies the result code of an Apple Event.L [event_resultcode]N3class, id, target, wait_reply, and the event stringPe[event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] [event_resultcode] [/event] [event: class="CLas", id="ThID", target="TargetApp", wait_reply="true"] [event_resultcode] [/event] Apple_Event_Tag.mod must be installed to use this command. This tag is valid only within the [event: [/event] container. The event tag is described in the Lasso User Guide. FieldC SubstitutionD [field: ...] The [field: ] tag indicates which field should be substituted into the format file. The general form of the field tag is [field: InsertField], where the text InsertField is the actual name of a field. Field names are not case-sensitive. Everything between (and including) the square brackets will be replaced with the contents of the specified field. The field value comes from the database and layout that invoked the page. The database and layout tags are used to specify the source of t his data and the specific data depends upon some Lasso action that identifies a specific record; thus, the tag can be used only on a post-Lasso type format file. The syntax shown will display the current database value as the current value for the text input field, so it can be used as part of update format file. Related fields can also be displayed with the [field] tag in the format [field: RelationshipName::FieldName]. However, if this format is used and the related field is in a port al on the FileMaker Pro layout, the first related record from that portal will be the only one displayed. The contents of a related field can be displayed or updated in the same manner as a standard field. For example, on an update form an example field that is populated by a related field called would appear as follows: <input type="text size=30 name="contacts::name value="contacts::name"> The parameters smart, break, can be used to control how Lasso encod es (or does not encode) special characters found in that field. For example, field names may also be used to complete anchor and image tags, using : <a href="project/[field: InsertField", raw]">[field: InsertField"]</a> <a href="http://[field: InsertField", url]">Some text to anchor.</a> The field tag can be used within any other substitution tag. For instance, one can output the data from a field whose name is specified by another field: [field: (field: InsertField")] EFentheses can be used to clarify what parameters belong to which tag. J!Displays the contents of a field.L [field: ...]N/Name of the field. Accepts encoding parameters.O [FMP-Field: ...]PQ<input type="text" size=30 name="YourFieldName" value="[field: "YourFieldName"]"> <input type="text" size=30 name="YourFieldName" value="[field: "YourFieldName"]"> The [field: ] tag indicates which field should be substituted into the format file. The general form of the field tag is [field: InsertField], where the text InsertField is the actual name of a field. Field names are not case-sensitive. Everything between (and including) the square brackets will be replaced with the contents of the specified field. The field value comes from the database and layout that invoked the page. The database and layout tags are used to specify the source of this data and the specific data depends upon some Lasso action that identifies a specific record; thus, the tag can be used only on a post-Lasso type format file. The syntax shown will display the current database value as the current value for the text input field, so it can be used as part of update format file. Related fields can also be displayed with the [field] tag in the format [field: RelationshipN ame::FieldName]. However, if this format is used and the related field is in a portal on the FileMaker Pro layout, the first related record from that portal will be the only one displayed. The contents of a related field can be displayed or updated in the same manner as a standard field. For example, on an update form an example field that is populated by a related field called would appear as follows: <input type="text size=30 name="contacts::name value="contacts::name"> parameters smart, break, can be used to control how Lasso encodes (or does not encode) special characters found in that field. For example, field names may also be used to complete anchor and image tags, using : <a href="project/[field: InsertField", raw]">[field: InsertField"]</a> <a href="http://[field: InsertField", url]">Some text to anchor.</a> The field tag can be used within any other substitution tag. For instance, one can output the data from a fieE ld whose name is specified by another field: [field: (field: InsertField")] Parentheses can be used to clarify what parameters belong to which tag. Display Field NameC SubstitutionD [field_name: ...] The [field_name: ] tag displays the number of fields in a specified database or a database field s name, type, or accessibility (protection). The first parameter to this tag must be either a number or the keyword count, which will return the total number of fields in the current layout. It is used in the format: [field_name: count] If there are ten fields on the specified layout, then the result is the number 10. Note that no actual field name is indicated. The number parameter rep resents the order of the fields on a layout. In other words, the following will display the name of the first field on the layout: [field_name: 1] This order is determined by the order in which fields were added to the layout. The numbering of the fields can be changed only by recreating the layout and placing the fields one at a time in the desired order. There are two other parameters which must be used along with the number. The parameter will output either text, number, image, date/time, boolean unknown depending on the type of data stored in the field. For example: [field_name: 1, type] The parameter protection will output if the field is modifiable, or read only if the data can not be modified (via an add or update). For example: [field_name: 1, protection] J!Displays a database field's name.L [field_name: ...]N+Parameters: count, number, type, protectionO [FMP-FieldName: ...]P [field_name: ...] [field_name: ...] The [field_name: ] tag displays the number of fields in a specified database or a database field s name, type, or accessibility (protection). The first parameter to this tag must be either a number or the keyword count, which will return the total number of fields in the current layout. It is used in the format: [field_name: count] If there are ten fields on the specified layout, then the result is the number 10. Note that no actual field name is indicated. The n umber parameter represents the order of the fields on a layout. In other words, the following will display the name of the first field on the layout: [field_name: 1] This order is determined by the order in which fields were added to the layout. The numbering of the fields can be changed only by recreating the layout and placing the fields one at a time in the desired order. There are two other parameters which must be used along with the number. The parameter will output eithe text, number, image, date/time, boolean unknown depending on the type of data stored in the field. For example: [field_name: 1, type] The parameter protection will output if the field is modifiable, or read only if the data can not be modified (via an add or update). For example: [field_name: 1, protection] Find All RecordsC ActionD -findall The -findall action finds all records in the specified FileMaker Pro database. The sample syntax shows how to submit a find all request with a button on an HTML form. The records are displayed using the format file specified by the -response tag (which should be some sort of hitlist). The -findall tag will use a default maximum records value of 50. In order to actually find all records in the database, pair -maxRecords with the value within an embedded URL or within the form. The sort field command can be used to determine how the records are displayed. Records will be left unsorted if the -sortfield command tag is not used, or is not given a value. In addition, -sortorder can also be used, with the values ascending, descending, custom to determine how to sort the results of a search. The default sort order is ascending if none are indicated. The -findall action can also be specified in an embedded URL which can be used in a hyperlink as follows: <a hre f="Lasso.acgi?-findall&-database=YourDBName&-layout=YourLayoutName &-response=YouFileName.html&-maxRecords=all&-sortfield=YourFieldName &-sortorder=ascending"> View all records in Database</a> The name of the submit button must be -findall and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-findall"> The name parameter must specify the action, even if the action is specified elsewhere. Security Considerations In order to execute the -findall action, the end user must have search permissions for the database. If the user does not, a database security violation error is returned. If any field in the database has been defined in the Lasso Security database with an exactsearch restriction, a security violation will be returned if the user tries to execute the -findall action. If a database has been assigned to the Lasso Security databas e and a field from that database is assigned an exactsearch restriction, then the -findall action cannot be used with that database, even if the field is included on a search form. J.Finds all records in a FileMaker Pro database.L -findallO -FindAllP6<input type="submit" name="-findall" value="Find All"> <input type="submit" name="-findall" value="Find All"> The -findall action finds all records in the specified FileMaker Pro database. The sample syntax shows how to submit a find all request with a button on an HTML form. The records are displayed using the format file specified by the -response tag (which should be some sort of hitlist). The -findall tag will use a default maximum records value of 50. In order to actually find all records in the database, pair -maxRecords with the va within an embedded URL or within the form. The sort field command can be used to determine how the records are displayed. Records will be left unsorted if the -sortfield command tag is not used, or is not given a value. In addition, -sortorder can also be used, with the values ascending, descending, custom to determine how to sort the results of a search. The default sort order is ascending if none are indicated. The -findall action can also be specified in an embedded URL which can be used in a hyperlink as follows: <a href="Lasso.acgi?-findall&-database=YourDBName&-layout=YourLayoutName &-response=YouFileName.html&-maxRecords=all&-sortfield=YourFieldName &-sortorder=ascending"> View all records in Database</a> The name of the submit button must be -findall and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-findall"> The name parameter must specify the action, even if the action is specified elsewhere. Security Considerations In order to execute the -findall action, the end user must have search permissions for the database. If the user does not, a database security violation error is returned. If any field in the database has been defined in the Lasso Security database with an exactsearch restriction, a security violation will be returned if the user tries to execute the -findall action. If a E database has been assigned to the Lasso Security database and a field from that database is assigned an exactsearch restriction, then the -findall action cannot be used with that database, even if the field is included on a search form. Form Parameter ValueC SubstitutionD [form_param: ...] The value which was submitted with a Lasso action can be retrieved by specifying the name of the field it was entered into. The value of the [form_param: ] tag can be entered into a field, paired with a Lasso command tag in an inline or URL link, or simply be displayed. The [form_param: ] is not set or specified on the previous page which contains the value within its form parameters. The source of the value is either a field on a form or the value that was paired to a field in an embedd ed URL or inline action. The value shown in the sample syntax YourFieldName is any field used on the previous format file. It can be the actual name of a field, or any made-up name if the data is not submitted to a database. For example, to use a form parameter from the data entered into a field called userid, use the following on the reply page: <input type="text size=30 name="name value="[form_param:"userid"]"> The previous value used for the userid field is thus made avai lable to be entered into the field. Following is another example. This time the value is entered into a URL link: <a href="action.lasso?-search&-database=employees&-layout=main&-response=detail.html& -op=eq&name=[form_param:"userid"]"> Search </a> A link is thus created that searches for the form parameter value in the field. count parameter can be used to return the number of values the specified [form_param: ] tag has. It is useful only multiple values are associ !ated with a particular form paramter. It appears in the format: [form_param: YourFieldName", count] Specific values can be retrieved using a number parameter. For example, the number 2, formatted as [form_param: paramName", 2], would return the second value associated with the field. JZInserts values from the previous HTTP submission into the currently processed format file.L [form_param: ...]N/Name of the field. Accepts encoding parameters.P [form_param:"YourFieldName"] [form_param:"YourFieldName"] The value which was submitted with a Lasso action can be retrieved by specifying the name of the field it was entered into. The value of the [form_param: ] tag can be entered into a field, paired with a Lasso command tag in an inline or URL link, or simply be displayed. The [form_param: ] is not set or specified on the previous page which contains the value within its form parameters. The source of the value is either a field on a form or the value that was paired to a field in an embedded URL or inline action. The value shown in the sample syntax YourFieldName is any field used on the previous format file. It can be the actual name of a field, or any made-up name if the data is not submitted to a database. For example, to use a form parameter from the data entered into a field called userid, use the following on the reply page: <input type="text size=30 name="name value="[form_param:"userid"]"> The previous value used for the serid field is thus made available to be entered into the field. Following is another example. This time the value is entered into a URL link: <a href="action.lasso?-search&-database=employees&-layout=main&-response=detail.html& -op=eq&name=[form_param:"userid"]"> Search </a> A link is thus created that searches for the form parameter value in the field. count parameter can be used to return the number of values the specified [form_param: ] tag has. It is useful o ?nly multiple values are associated with a particular form paramter. It appears in the format: [form_param: YourFieldName", count] Specific values can be retrieved using a number parameter. For example, the number 2, formatted as [form_param: paramName", 2], would return the second value associated with the field. HTTP Header C ContainerD [header]E [/header] The HTTP header can be determined using the [header] [/header] tag pair in a response file. The text between the [header] container will become the HTTP header for the response file. The header text must be in a format supported by the HTTP standard protocol. The various requests are are determined by the status line which is made up of the following: <http version> <status code> <reason line> These three elements are delimited by a single blank space. Example uses of headers include allowing a form to be submitted without reloading or redirecting the current page, refreshing the current page, resetting the content of a form, or prompting for new authentication values to replace the current settings saved in the Web browser. The sample syntax shows another example. This header redirects a Lasso action to another URL to carry out a second action, in this case it initiates a Lasso add action. Note the following about this syntax: is the same URL as Location" ; it is repeated since some browsers do not recognize one or the other form. The field specified by [field:"fieldname",url] must be found on the database and layout in the previous format file since the value is substituted into the URL. The header URL must not contain any spaces, nor should there be any spaces at the start of each line. The Server line is an optional element for a redirect. After this page loads it adds a record to the specified database and immediately callDEs up the second response format file, in this case, Add_Reply.html." J'Determines the HTTP header information.L [header] ... [/header]N.Within container: Specify standard HTTP headerO [FMP-Header] [/FMP-Header] [header] http/1.0 302 found Location: http://www.domain.com/action.lasso?-database=YourDBName&-layout=YourLayoutName& -response=Pathto/FileName.html&YourFieldName=[field:"fieldname",url]&-token=[token_value,url]&-add URI: http://www.domain.com/action.lasso?-database=YourDBName&-layout=YourLayoutName& -response=Pathto/FileName.html&YourFieldName=[field:"fieldname",url]&-token=[token_value,url]&-add Server: Webstar/2.0 ID/CGI [/header]  [header] http/1.0 302 found Location: http://www.domain.com/action.lasso?-database=YourDBName&-layout=YourLayoutName& -response=Pathto/FileName.html&YourFieldName=[field:"fieldname",url]&-token=[token_value,url]&-add URI: http://www.domain.com/action.lasso?-database=YourDBName&-layout=YourLayoutName& -response=Pathto/FileName.html&YourFieldName=[field:"fieldname",url]&-token=[token_value,url]&-add Server: Webstar/2.0 ID/CGI [/header]  The HTTP header can be determined using the [header] [/header] tag pair in a response file. The text between the [header] container will become the HTTP header for the response file. The header text must be in a format supported by the HTTP standard protocol. The various requests are are determined by the status line which is made up of the following: <http version> <status code> <reason line> These three elements are delimited by a single blank space. Example uses of headers include allowing a form to be submitted without reloading or redirecting the current page, refreshing the current page, resetting the content of a form, or prompting for new authentication values to replace the current settings saved in the Web browser. The sample syntax shows another example. This header redirects a Lasso action to another URL to carry out a second action, in this case it initiates a Lasso add action. Note the following about this syntax: is the same URL as Location" ; it is repeated since some browsers do not recognize one or the other form. The field specified by [field:"fieldname",url] must be found on the database and layout in the previous format file since the value is substituted into the URL. The header URL must not contain any spaces, nor should there be any spaces at the start of each line. The Server line is an optional element for a redirect. After this page loads it adds a record to the specified database and immediately call EEs up the second response format file, in this case, Add_Reply.html." HTML CommentC ContainerD [html_comment]E [/html_comment] When an [include: ..] file is included into another file, Lasso will also include any text enclosed within HTML comments. However, Lasso will ignore any text or tags contained within the commented area (as is the case with an HTML page). The [html_comment] [/html_comment] container tag can be used to have Lasso process any contained Lasso tags, and then place all contained text within an HTML comments bracket. In other words, the [html_comment] [/html_comment] container tags will be subs tituted by opening and closing comment symbols after the format file is processed by Lasso. For example: [html_comment] Date is [server_date] [/html_comment] will result in:  The usefulness of this is primarily to accommodate JavaScripts, which must be enclosed in comments so they are not processed by older Web browsers. In certain cases, a value returned by Lasso may be needed in a JavaScript. This tag allows for Lasso to process commented text, as well as pC@reserve those comments in the file that is output to the server. J,Processes tags located within HTML comments.L"[html_comment] ... [/html_comment]P [html_comment] [/html_comment] [html_comment] [/html_comment] When an [include: ..] file is included into another file, Lasso will also include any text enclosed within HTML comments. However, Lasso will ignore any text or tags contained within the commented area (as is the case with an HTML page). The [html_comment] [/html_comment] container tag can be used to have Lasso process any contained Lasso tags, and then place all contained text within an HTML comments bracket. In other words, the [html_comment] [/html_co mment] container tags will be substituted by opening and closing comment symbols after the format file is processed by Lasso. For example: [html_comment] Date is [server_date] [/html_comment] will result in:  The usefulness of this is primarily to accommodate JavaScripts, which must be enclosed in comments so they are not processed by older Web browsers. In certain cases, a value returned by Lasso may be needed in a JavaScript. This tag allows for Lasso to pr Cbocess commented text, as well as preserve those comments in the file that is output to the server. Conditional StatementC ContainerD [if: ...]E [/if] The Lasso container tags [if] [else] [/if] control what is displayed or included on a file that is processed by Lasso. These tags can only be used on post-Lasso format files that are returned by Lasso. When a Lasso action is submitted, the conditional tags direct Lasso to evaluate the conditional expression and return specific data or a particular message if the condition is met. If the condition evaluates to false, then the HTML which follows the [else] or [else: if: ] command is refer enced. The general form of the tag is: [if: (comparison-value) operator (comparison-value)] HTML if condition is true [else] HTML if condition is false [/if] Note: The [/if] tag cannot be referenced as [endif] as was possible in previous versions of Lasso. A conditional statement consists of the comparison fields that appear on either side of the comparison pair and the operator that determines how to compare those values. The comparison value can either be a hard-coded liter al value, a value returned for a FileMaker Pro field, or a Lasso substitution tag. Comparison values are not case sensitive and can include spaces within literal values. Quotes should be placed around values or string literals to designate the start and end of the comparison value. To specify a field, use the field tag, followed by a colon, and then the name of the field in quotes, as follows: [if: field:"Assets > field:"Liabilities"] The field value is from the previous format file that called up the page where your conditional tags are placed. Lasso tags can be used if they are substituted with a value when returned. For example, nfound, client_id can be used, but not [record] or [portal: ] tags. Don t use brackets to enclose Lasso tags within tags. The operator is how the comparison is made and is used in the short form. The comparison has several operator options: equal to (==), not equal to (!=), greater than (>), greater than or equal (>=), less tha n (<), less than or equal to (<=), and contains (>>) Multiple conditional statements can be combined using the concatenation symbols. These symbols serve as a logical operator between expressions to determine if the entire expression is true if all are true (the symbol means ), or if just one of the conditions are true (the symbol means or"). Parentheses can be used to determine the order that the comparison occurs. For example: [if: value1 < value2 && ( va lue3 == value4 || value5 > value1)] display this [/if] Expressions in the most-nested parentheses will be evaluated first. If conditional statements can also be nested as follows: [if: (comparison-value) operator (comparison-value)] [if: (comparison-value) operator (comparison-value)] HTML if condition is true [else] HTML if condition is false [/if] [/if] To simplify a complex series of nested expressions, nested conditional statements can be added to the else ta g, using the format [else: if: condition]. With this format the first condition is evaluated, if it is false, the condition in the first [else: if:] tag is evaluated. If true, the enclosed tags and text is used. If false, the next else statement is evaluated. This continues until there is a final statement. For example: [if: condition] text or tags [else: if: condition] text or tags [else: if: condition] text or tags [else] text or tags [/if] 5JCControls the conditions of what is displayed or included in a file.L [if: ...] ... [/if]N The conditional expression made up of a value, operator, and the comparison value. Within the container: what should display if condition is true.O [FMP-If: ...] [/FMP-If]P [if: field: "YourFieldName" operator "value"] ...HTML if condition is true... [else] ...HTML if condition is false... [/if] [if: field: "YourFieldName" operator "value"] ...HTML if condition is true... [else] ...HTML if condition is false... [/if] The Lasso container tags [if] [else] [/if] control what is displayed or included on a file that is processed by Lasso. These tags can only be used on post-Lasso format files that are returned by Lasso. When a Lasso action is submitted, the conditional tags direct Lasso to evaluate the conditional expression and return specific data or a particular message if the condition is met. If the condition evaluates to false, then the HTML which follows the [else] or [else: if: ] command is referenced. The general form of the tag is: [if: (comparison-value) operator (comparison-value)] HTML if condition is true [else] HTML if condition is false [/if] Note: The [/if] tag cannot be referenced as [endif] as was possible in previous versions of Lasso. A conditional statement consists of the comparison fields that appear on either side of the comparison pair and the operator that determines how to compare those values. The comparison value can either be a hard-coded literal value, a value returned for a FileMaker Pro field, or a Lasso substitution tag. Comparison values are not case sensitive and can include spaces within literal values. Quotes should be placed around values or string literals to designate the start and end of the comparison value. To specify a field, use the field tag, followed by a colon, and then the name of the field in quotes, as follows: [if: field:"Assets > field:"Liabilities"] The field value is from the previous format file that called up the page where your conditional tags are placed. Lasso tags can be used if they are substituted with a value when returned. For example, nfound, client_id can be used, but not [record] or [portal: ] tags. Don t use brackets to enclose Lasso tags within tags. The operator is how the comparison is made and is used in the short form. The comparison has several operator options: equal to (==), not equal to (!=), greater than (>), greater than or equal (>=), less than (<), less than or equal to (<=), and contains (>>) Multiple conditional statements can be combined using the concatenation symbols. These symbols serve as a logical operator between expressions to determine if the entire expression is true if all are true (the symbol means ), or if just one of the conditions are true (the symbol means or"). Parentheses can be used to determine the order that the comparison occurs. For example: [if: value1 < value2 && ( value3 == value4 || value5 > value1)] display this [/if] Expressions in the most-nested parentheses will be evaluated first. If conditional statements can also be nested as follows: [if: (comparison-value) operator (comparison-value)] [if: (comparison-value) operator (comparison-value)] HTML if condition is true [else] HTML if condition is false [/if] [/if] To simplify a complex series of nested expressions, nested conditional statements can be added to the else tag, using the format [else: if: condition]. With this format the first condition is evaluated, if it is false, the condition in the first [else: if:] tag is evaluated. If true, the enclosed tags and text is used. If false, the next else statement is evaluated. This continues until there is a final statement. For example: [if: condition] text or tags Hi[else: if: condition] text or tags [else: if: condition] text or tags [else] text or tags [/if] Image ActionC ActionD -image image action tag is usually not specified as other action tags, since it only appears when substituted into a file by the [image: ] tag. When the [image: ] substitution tag is processed, a link is automatically created to point a specific graphic located in a FileMaker Pro container field. If you open the source of the document returned by Lasso you can see the form used by Lasso to display the image: <img src="/employees/action.lasso?-database=Employees&-recid=12&Photo=jpeg&-imagB align=left> In the above, the -recid tag identifies which record the image is found on, and photo identifies the graphic format used. Lasso automatically sets up an embedded URL link that uses an -image action to retrieve and convert the image. Creates a link to an image.L -imageO 6Pf<img src="action.lasso?-image&-database=Employees&-recid=[recid_value]&YourFieldName=jpeg" align=left> <img src="action.lasso?-image&-database=Employees&-recid=[recid_value]&YourFieldName=jpeg" align=left> image action tag is usually not specified as other action tags, since it only appears when substituted into a file by the [image: ] tag. When the [image: ] substitution tag is processed, a link is automatically created to point a specific graphic located in a FileMaker Pro container field. If you open the source of the document returned by Lasso you can see the form used by Lasso b to display the image: <img src="/employees/action.lasso?-database=Employees&-recid=12&Photo=jpeg&-image align=left> In the above, the -recid tag identifies which record the image is found on, and photo identifies the graphic format used. Lasso automatically sets up an embedded URL link that uses an -image action to retrieve and convert the image. ImageC Substitution [image: ...] Lasso has the ability to directly serve FileMaker Pro pictures to Web browsers using the [image: ] tag. Graphics are stored in a FileMaker Pro container field as a PICT file. When a Lasso action is called the picture is automatically converted to JPEG, a standard Internet graphic format. Or, to GIF format using an intermediary program clip2gif. The [image: ] tag is used to specify which FileMaker Pro field contains the PICT image. The [image: ] tag is specified in a manner similar t o the [field: ] tag, for example: <img src="[image: YourFieldName"]"> Specify the field name that contains the image, then optional parameters. Use to convert PICT images to the file type; if is indicated, you must have clip2gif installed. Additional parameters can be used with the parameter to control the amount of compression. Specify 16 or 32 as the bit depth for each pixel. The default is 16. Specify a number 0 through 4 for the compression amount. 0 yie lds the best quality, but results in larger files, while 4 yields satisfactory quality for smaller files. The default is 4. Some examples: [image: YourFieldName", jpeg, 16, 0] [image: YourFieldName", jpeg, 32, 4] [image: YourFieldName", jpeg, 16, 4] (equivalent to [image: YourFieldName"]) For GIF images, clip2gif must be installed on the Mac OS Web server. Lasso cannot translate PICT files to the GIF format. There are additional parameters available for the parameter. Specify false for interlaced or non-interlaced; the default is false (non-interlaced). Also, for GIF images, specify 1, 2, 4, or 8 for the bit-depth of the image; the default is 8. Some examples: [image: YourFieldName", gif, true, 4] [image: YourFieldName", gif, false, 2] [image: YourFieldName", gif, false, 8] Additional HTML elements can be included within this syntax. For example, the width and height can be indicated as follows: <img src="[image: YourFieldName"] height="2 width="20% border="1"> When the [image: ] substitution tag is processed, a link is automatically created to point a specific graphic located in a FileMaker Pro container field. If you open the source of the document returned by Lasso you can see the form used by Lasso to display the image: <img src="/employees/action.lasso?-database=Employees&-recid=12&Photo=jpeg&-image align=left> In the above, the -recid tag identifies which record the image is found on, and photo identifie s the graphic format used. Lasso automatically sets up an embedded URL link that uses an -image action to retrieve and convert the image. J(Displays an image from a database field.L [image: ...]N Name of the image field. Parameters: encoding, jpeg (16 or 32 bit depth 0 - 4 for compression), gif (true or false for interlaced , 1, 2, 4, or 8 for the bit-depth)O [FMP-Image: ...]P&<img src="[image:YourFieldName,jpeg]"> <img src="[image:YourFieldName,jpeg]"> Lasso has the ability to directly serve FileMaker Pro pictures to Web browsers using the [image: ] tag. Graphics are stored in a FileMaker Pro container field as a PICT file. When a Lasso action is called the picture is automatically converted to JPEG, a standard Internet graphic format. Or, to GIF format using an intermediary program clip2gif. The [image: ] tag is used to specify which FileMaker Pro field contains the PICT image. The [image: ] tag is specified in a manner similar to the [field: ] tag, for example: <img src="[image: YourFieldName"]"> Specify the field name that contains the image, then optional parameters. Use to convert PICT images to the file type; if is indicated, you must have clip2gif installed. Additional parameters can be used with the parameter to control the amount of compression. Specify 16 or 32 as the bit depth for each pixel. The default is 16. Specify a number 0 thr ough 4 for the compression amount. 0 yields the best quality, but results in larger files, while 4 yields satisfactory quality for smaller files. The default is 4. Some examples: [image: YourFieldName", jpeg, 16, 0] [image: YourFieldName", jpeg, 32, 4] [image: YourFieldName", jpeg, 16, 4] (equivalent to [image: YourFieldName"]) For GIF images, clip2gif must be installed on the Mac OS Web server. Lasso cannot translate PICT files to the GIF format. There are additional parameters ava ilable for the parameter. Specify false for interlaced or non-interlaced; the default is false (non-interlaced). Also, for GIF images, specify 1, 2, 4, or 8 for the bit-depth of the image; the default is 8. Some examples: [image: YourFieldName", gif, true, 4] [image: YourFieldName", gif, false, 2] [image: YourFieldName", gif, false, 8] Additional HTML elements can be included within this syntax. For example, the width and height can be indicated as follows: <img src="[image: YourFieldName"] height="20% width="20% border="1"> When the [image: ] substitution tag is processed, a link is automatically created to point a specific graphic located in a FileMaker Pro container field. If you open the source of the document returned by Lasso you can see the form used by Lasso to display the image: <img src="/employees/action.lasso?-database=Employees&-recid=12&Photo=jpeg&-image align=left> In the above, the -recid tag identifies which record the image is found on, and photo identifies the graphic format used. Lasso automatically sets up an embedded URL link that uses an -image action to retrieve and convert the image. Include a FileC SubstitutionD [include: ...] The [include: ] substitution tag will combine another file with the format file processed by Lasso.When the [include] tag appears on a file processed by Lasso, the contents of the referenced file will be displayed in place of the [include: ] tag syntax. The following notes cover some of the details on constructing the [include] tag: This tag can occur only in a file processed by Lasso, as it must be generated as the result of a Lasso action. A path to the included file must be spe cified. However, as is the case with response files, the file is considered to be a relative location. Thus, if the include file is in the same location as the file specifying it, then only the name of the file needs to be specified. The file specified by [include] must be located within the Web serving folder. [include] cannot specify a URL. The included file can be any type of file and does not need to contain HTML. However, HTML may be needed to format text or specify images. The [include] tag can be nested; that is, if the included file also contains an [include] tag, then that additional file will also be displayed. To revert to Lasso s previous non-relative behavior, the NR_Include_Tag.mod should be placed in the Lasso Modules folder (and Lasso re-launched). This compatibility module uses the previous rules for specifying paths to include files, in which the path is always from the Lasso application. The only advantage to using this module is when using format files created by an earlier version of Lasso. It is recommended, however, that those files be updated and the NR_Include_Tag.mod not be used. Setting up HTML files using [include] files is an intelligent means for making quick and painless global updates to all dynamically served files by simply changing the contents of one referenced [include] file. An example of how this might be useful is demonstrated in the supplied Employees database example, where various format filesEV reference an include file called footer.txt that supplies a footer for every page. J>Combines another file with the format file processed by Lasso.L [include: ...]N The name and path to a fileO [FMP-Include: ...]P%[include: "Pathto/YourFileName.html"] [include: "Pathto/YourFileName.html"] The [include: ] substitution tag will combine another file with the format file processed by Lasso.When the [include] tag appears on a file processed by Lasso, the contents of the referenced file will be displayed in place of the [include: ] tag syntax. The following notes cover some of the details on constructing the [include] tag: This tag can occur only in a file processed by Lasso, as it must be generated as the result of a Lasso action. A path to the included file must be specified. However, as is the case with response files, the file is considered to be a relative location. Thus, if the include file is in the same location as the file specifying it, then only the name of the file needs to be specified. The file specified by [include] must be located within the Web serving folder. [include] cannot specify a URL. The included file can be any type of file and does not need to contain HTML. However, HTML may be n eeded to format text or specify images. The [include] tag can be nested; that is, if the included file also contains an [include] tag, then that additional file will also be displayed. To revert to Lasso s previous non-relative behavior, the NR_Include_Tag.mod should be placed in the Lasso Modules folder (and Lasso re-launched). This compatibility module uses the previous rules for specifying paths to include files, in which the path is always from the Lasso application. The only advantage to using this module is when using format files created by an earlier version of Lasso. It is recommended, however, that those files be updated and the NR_Include_Tag.mod not be used. Setting up HTML files using [include] files is an intelligent means for making quick and painless global updates to all dynamically served files by simply changing the contents of one referenced [include] file. An example of how this might be useful is demonstrated in the supplied Employees datab E}ase example, where various format files reference an include file called footer.txt that supplies a footer for every page. InlineC ContainerD [inline: ...]E [/inline] While processing a format file, Lasso will perform an additional Lasso action specified by the [inline: [/inline] container tag. Thus, the [inline] tag provides the ability to process multiple Lasso actions within a single format file. The [inline] tag can be placed in any file processed by Lasso. Anything between the [inline] tag and the [/inline] tag is processed as if it were an entirely separate response format file that is returned by the action specified in the inline. The eleme nts of an inline tag are similar to the construction of an embedded URL, in which values are paired with named parameters. The following parameters must be specified when using the [inline] tag: database the name of the database to operate on. layout the layout to operate on. The remaining name=value pairs specify the database field names and values, the sort, the maximum records returned per group, etc., and any of the various other Lasso command tags. Response does not need t o be specified since there is none. Any action also needs to be specified, or Lasso will use the nothing action (and process the request but not interact with a database). When Lasso returns the page, Lasso automatically transforms the name=value pairs into an embedded URL that carries out some action (this is not visible in the source file or at any other point). That action occurs as the page is being processed by Lasso. Note that the construction of inlines differs from embedded UR Ls. Keep in mind the following important points: The name=value pairs, and the Lasso action, are separated by commas. Literal values, including any field names, should be surrounded by quotes to indicate that the value is not a tag. Quotes are optional but make it quicker for Lasso to determine that the text is a literal value rather than a tag. Quotes must be used if the value may be confused with a Lasso tag. Do not use quotes around Lasso tags. Substitution fields using t field tag to substitute in the current value of a field must use the tag name field followed by a colon (i.e., field:"category"), and the name of the field in quotes. Do not use any square brackets within other square brackets. Similarly, do not use dashes before action or command tags. To test the result of an inline action, see the [inline_result] tag. Inlines do not need to be URL encoded. However, they can be encoded with the smart parameter if you want the Lvalue to be stored or passed encoded in that fashion. Or, to prevent any encoding, use the parameter. To do so, simply add the parameter and separate it with a comma: [inline: database="jobs.fp3", layout="main", message"=(field:"sent", raw ), add] The field that uses the parameter should be separated by parentheses. J7Performs additional Lasso actions within a format file.L [inline: ...] ... [/inline]NBA Lasso action statement. Within the container: any text or tags. AV[inline: database=database_name, layout=layout_name, "name"="value", action] [/inline] [inline: database=database_name, layout=layout_name, "name"="value", action] [/inline] While processing a format file, Lasso will perform an additional Lasso action specified by the [inline: [/inline] container tag. Thus, the [inline] tag provides the ability to process multiple Lasso actions within a single format file. The [inline] tag can be placed in any file processed by Lasso. Anything between the [inline] tag and the [/inline] tag is processed as if it were an entirely separate response format file that is returned by the action specified in the inline. The elements of an inline tag are similar to the construction of an embedded URL, in which values are paired with named parameters. The following parameters must be specified when using the [inline] tag: database the name of the database to operate on. layout the layout to operate on. The remaining name=value pairs specify the database field names and values, the sort, the maximum records returned pe r group, etc., and any of the various other Lasso command tags. Response does not need to be specified since there is none. Any action also needs to be specified, or Lasso will use the nothing action (and process the request but not interact with a database). When Lasso returns the page, Lasso automatically transforms the name=value pairs into an embedded URL that carries out some action (this is not visible in the source file or at any other point). That action occurs as the page is b eing processed by Lasso. Note that the construction of inlines differs from embedded URLs. Keep in mind the following important points: The name=value pairs, and the Lasso action, are separated by commas. Literal values, including any field names, should be surrounded by quotes to indicate that the value is not a tag. Quotes are optional but make it quicker for Lasso to determine that the text is a literal value rather than a tag. Quotes must be used if the value may be confused w ith a Lasso tag. Do not use quotes around Lasso tags. Substitution fields using the field tag to substitute in the current value of a field must use the tag name field followed by a colon (i.e., field:"category"), and the name of the field in quotes. Do not use any square brackets within other square brackets. Similarly, do not use dashes before action or command tags. To test the result of an inline action, see the [inline_result] tag. Inlines do not need to be URL en coded. However, they can be encoded with the smart parameter if you want the value to be stored or passed encoded in that fashion. Or, to prevent any encoding, use the parameter. To do so, simply add the parameter and separate it with a comma: [inline: database="jobs.fp3", layout="main", message"=(field:"sent", raw ), add] The field that uses the parameter should be separated by parentheses. Inline ResultC SubstitutionD [inline_result] The [inline_result] reports on the success of an action on any format file.If the action is unsuccessful, the type of error which occurred is displayed. The [inline_result] tag can be used within the [inline] [/inline] tags as a means to test the results of an inline action. It can also be used outside of an inline tag and will report as follows: If there are no results of a search: errAENoSuchObject (-noresults) If a required field is missing: errRequiredFieldMissing (-reqFieldMi ssing) If an error occurs with a date entered in the incorrect format: -17005 (-adderror) A conditional statement can check the success of the inline action as follows: [inline: database="employees", layout="web", username"="john", search] [if: inline_result=="noErr"] do something [else] [/if] [/inline] Another way to test an inline, is to convert it to an embedded URL to determine if that works to complete the Lasso action successfully. To do so, separate the name value pair ps with ampersands (instead of commas) and remove all quotes and spaces (unless a space is part of a database, layout, or file name; these spaces should be encoded as %20). For example, the inline shown above can be transformed to: <a href="action.lasso?database=employees&layout=web&username=john&search>check link</a> Refer to the [inline: ] tag for more details. J*Displays the result of an [inline] action.L [inline_result]P [inline: database="YourDBName", layout="YourLayoutName", "name"="value", action] [if: inline_result=="noerr"] ...do something [else]Error: [inline_result] [/if] [/inline] [inline: database="YourDBName", layout="YourLayoutName", "name"="value", action] [if: inline_result=="noerr"] ...do something [else]Error: [inline_result] [/if] [/inline] The [inline_result] reports on the success of an action on any format file.If the action is unsuccessful, the type of error which occurred is displayed. The [inline_result] tag can be used within the [inline] [/inline] tags as a means to test the results of an inline action. It can also be used outside of an inlin e tag and will report as follows: If there are no results of a search: errAENoSuchObject (-noresults) If a required field is missing: errRequiredFieldMissing (-reqFieldMissing) If an error occurs with a date entered in the incorrect format: -17005 (-adderror) A conditional statement can check the success of the inline action as follows: [inline: database="employees", layout="web", username"="john", search] [if: inline_result=="noErr"] do something [else] [/if] [/inline] Another way to test an inline, is to convert it to an embedded URL to determine if that works to complete the Lasso action successfully. To do so, separate the name value pairs with ampersands (instead of commas) and remove all quotes and spaces (unless a space is part of a database, layout, or file name; these spaces should be encoded as %20). For example, the inline shown above can be transformed to: <a href="action.lasso?database=employees&layout=web&username=john&search>check link</aD2> Refer to the [inline: ] tag for more details. Display Lasso ActionC SubstitutionD [lasso_action] The current action can be inserted into the reply page as Lasso processes a response format file.Its value will be one of the available Lasso actions such as search, update, delete, show. This value can be used only on a form that was generated via Lasso (post-Lasso). The current action can simply be displayed or saved in a database, for example, a log database that records Lasso activity. The action can be displayed using: [lasso_action] One advantage of using this tag p is when used within [if] conditional statements. A returned HTML file can be dynamically altered depending on the action that was used to invoke the format file. For example: [if: lasso_action == value"] display one thing [else] [/if] Also, using lasso_action with an [if] tag will allow you to take different actions depending on what the current action is. J<Substitutes the current action into the page being processedL [lasso_action]O [FMP-CurrentAction]P [lasso_action] [lasso_action] The current action can be inserted into the reply page as Lasso processes a response format file.Its value will be one of the available Lasso actions such as search, update, delete, show. This value can be used only on a form that was generated via Lasso (post-Lasso). The current action can simply be displayed or saved in a database, for example, a log database that records Lasso activity. The action can be displayed using: [lasso_action] One advantage o f using this tag is when used within [if] conditional statements. A returned HTML file can be dynamically altered depending on the action that was used to invoke the format file. For example: [if: lasso_action == value"] display one thing [else] [/if] Also, using lasso_action with an [if] tag will allow you to take different actions depending on what the current action is. Lasso ProcessC SubstitutionD [lasso_process: ...] The [lasso_process: ] tag can be used to instruct Lasso to process any enclosed tags, and to display the result. The greatest utility of this tag is to process Lasso tags that are contained in a field and returned to a format file. In this case, any Lasso tags will be processed on the current format file. For example, if you had a field named result and this field contained Lasso tags, the following syntax could be used to process any tags that are contained in this field: [lasso_procB ess: field:"result"] The result is the same as if the contents of the field were part of the original format file when it was processed. J;Processes the specified parameters and displays the result.L [lasso_process: ...]N Any un-named parametersP [lasso_process: ...] [lasso_process: ...] The [lasso_process: ] tag can be used to instruct Lasso to process any enclosed tags, and to display the result. The greatest utility of this tag is to process Lasso tags that are contained in a field and returned to a format file. In this case, any Lasso tags will be processed on the current format file. For example, if you had a field named result and this field contained Lasso tags, the following syntax could be used to process any tags that are contained in thiB s field: [lasso_process: field:"result"] The result is the same as if the contents of the field were part of the original format file when it was processed. Submit PasswordC CommandD -lassopasswordI/See the description for the -lassousername tag.J'Sets the password for Lasso Security. L -lassopasswordP <input type="hidden" name="-lassousername" value="some_username"> <input type="hidden" name="-lassopassword" value="some_password"> <input type="hidden" name="-lassousername" value="some_username"> <input type="hidden" name="-lassopassword" value="some_password"> See the description for the -lassousername tag. Submit UsernameC CommandD -lassousername If Lasso Security is initialized, Lasso will check the access privileges of the current user to a specific database, when the database is first accessed. The values it checks are set by the user authentication process and sent by the Web browser in the HTTP stream. The username and password values are checked against those stored in the Lasso Security database. The -lassousername and -lassopassword tags can be used to submit the the user authentication values with a Lasso action. In othe r words, the values used for checking access privileges to a database that is protected by can be set in a Lasso action. The -lassousername tag is used to set the username, while -lassopassword is used to set the password used in the security check. If either are not specified, and a username and password is required, standard browser authentication will be used. The value used for these tags can be a hard-coded literal value or returned from a database field. For example, if a busine database is set up to require an exact search for the and fields, a search can still occur with an embedded URL link by using the following syntax: <a href="action.lasso?-search&-database=business&-layout=main&-response=detail.html&-op=eq& name=[field:name]&-lassousername=admin&-lassopassword=pass"> Search </a> Note that in this example admin and are sample values, and are those found in the Lasso Security database for the username and password for the busines database. The tags could be used in a Lasso action specified within an [inline: ] tag as follows: [inline: database="business", layout="main", leads="top", lassousername="admin", lassopassword="goahead", search] [If: inline_result="noErr"] [record] Top Leads = [field:"name"]<br> [/record] [else] [/if] [/inline] J'Sets the username for Lasso Security. L -lassousernameP <input type="hidden" name="-lassousername" value="some_username"> <input type="hidden" name="-lassopassword" value="some_password"> <input type="hidden" name="-lassousername" value="some_username"> <input type="hidden" name="-lassopassword" value="some_password"> If Lasso Security is initialized, Lasso will check the access privileges of the current user to a specific database, when the database is first accessed. The values it checks are set by the user authentication process and sent by the Web browser in the HTTP stream. The username and password values are checked against those stored in the Lasso Security datab ase. The -lassousername and -lassopassword tags can be used to submit the the user authentication values with a Lasso action. In other words, the values used for checking access privileges to a database that is protected by can be set in a Lasso action. The -lassousername tag is used to set the username, while -lassopassword is used to set the password used in the security check. If either are not specified, and a username and password is required, standard browser authentication will be used. The value used for these tags can be a hard-coded literal value or returned from a database field. For example, if a business database is set up to require an exact search for the and fields, a search can still occur with an embedded URL link by using the following syntax: <a href="action.lasso?-search&-database=business&-layout=main&-response=detail.html&-op=eq& name=[field:name]&-lassousername=admin&-lassopassword=pass"> Search </a> Note that in this example and are sample values, and are those found in the Lasso Security database for the username and password for the business database. The tags could be used in a Lasso action specified within an [inline: ] tag as follows: [inline: database="business", layout="main", leads="top", lassousername="admin", lassopassword="goahead", search] [If: inline_result="noErr"] [record] Top Leads = [field:"name"]<br> [/record] [else] [/if] [/inline] Display Database Layout Sub-ContainerD [lay_name] ?The [lay_name] tag can be used only within the [lay_names: [/lay_names] container tags to display the name of the specified layout. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. JWDisplays the name of the specified layout in conjunction with the [lay_names: ...] tag.L [lay_name]N&Is a tag in the Database_Info_Tags.modO (internal to web companion)P5[lay_names: YourDBName] [lay_name]<br> [/lay_names] v[lay_names: YourDBName] [lay_name]<br> [/lay_names] The [lay_name] tag can be used only within the [lay_names: [/lay_names] container tags to display the name of the specified layout. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. Display All Layout Names @C ContainerD [lay_names: ...]E [/lay_names] The [lay_names: ] tag is used to retrieve the names of all layouts in the specified database. The [lay_name] tag will be substituted for the layout names. The [lay_name] tag can only used within the [lay_names: [/lay_names] container tags. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. This tag is part of the Database Information Tags module and is oBunly available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. J=Retrieves the names of all layouts in the specified database.L![lay_names: ...] ... [/lay_names]NkName of database. Within container: the [lay_name] substitution tag. Is a tag in the Database_Info_Tags.modO (internal to web companion)P4[lay_names: thedbname] [lay_name]<br> [/lay_names] [lay_names: thedbname] [lay_name]<br> [/lay_names] The [lay_names: ] tag is used to retrieve the names of all layouts in the specified database. The [lay_name] tag will be substituted for the layout names. The [lay_name] tag can only used within the [lay_names: [/lay_names] container tags. This tag is part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. This tag is B part of the Database Information Tags module and is only available if the Database_Info_Tags.mod file is located with the Lasso Modules folder when Lasso is launched. Specify LayoutC CommandD -layout The -layout tag instructs Lasso as to which layout to use from the specified database. Only one layout can be specified for a single action. The name is not case-sensitive. To avoid confusion, do not give your database and layout the same name. Also, do not use ampersands, slashes, or other extended characters in database, layout, or field names, or field values. All other special characters should be encoded. Although -layout is optional, it is recommended. If the layout is not specified, then Lasso will use layout 0 (zero). When using layout 0, Lasso will be unable to refer to summary fields, related fields, calculation fields, auto-entered fields, etc. Each layout should have at least all of the fields needed to complete the particular Lasso action. For example: format files The FileMaker Pro database layout must contain all the fields specified in the add format file, AND all fields specified in the format file specified by the -response command tag. If a fie ld is specified that is not on the layout, the add will occur but the data that was entered for the missing field will be lost. Search format files The FileMaker Pro database layout must contain all fields that are returned on the hitlist format file. Lasso will read all fields on the layout specified with the layout tag on the search page; therefore, do not include any fields that are not used for the search parameters or hitlist page (these can be shown on a subsequent detail page bDPy changing the layout referenced on the hitlist page for the [detail_link] tag). JFInstructs Lasso as to which layout to use from the specified database.L -layoutO -LayP;<input type="hidden" name="-layout" value="YourLayoutName"> <input type="hidden" name="-layout" value="YourLayoutName"> The -layout tag instructs Lasso as to which layout to use from the specified database. Only one layout can be specified for a single action. The name is not case-sensitive. To avoid confusion, do not give your database and layout the same name. Also, do not use ampersands, slashes, or other extended characters in database, layout, or field names, or field values. All other special characters should be encoded. Although -layout is optional, it is recommended. If the layout is not specified, then Lasso will use layout 0 (zero). When using layout 0, Lasso will be unable to refer to summary fields, related fields, calculation fields, auto-entered fields, etc. Each layout should have at least all of the fields needed to complete the particular Lasso action. For example: format files The FileMaker Pro database layout must contain all the fields specified in the add format file, AND all fields specified in the format file specified by the -response command tag. If a field is specified that is not on the layout, the add will occur but the data that was entered for the missing field will be lost. Search format files The FileMaker Pro database layout must contain all fields that are returned on the hitlist format file. Lasso will read all fields on the layout specified with the layout tag on the search page; therefore, do not include any fields that are not used for the search parameters or hD itlist page (these can be shown on a subsequent detail page by changing the layout referenced on the hitlist page for the [detail_link] tag). Display Layout NameC SubstitutionD [layout_name] As Lasso processes a response format file, the [layout_name] tag will be substituted for the name of the layout that was referenced. This value can be used only on a form that was generated via Lasso (post-Lasso) and is determined by the layout specified on the previous action. The value could simply be displayed, or entered into a field, for example a log database that records Lasso activity. Or, it could be used in a conditional statement to determine the HTML output. J9Substitutes the layout used in the previous Lasso action.L [layout_name]N Accepts encoding parameters.O [FMP-CurrentLayout]P [layout_name] [layout_name] As Lasso processes a response format file, the [layout_name] tag will be substituted for the name of the layout that was referenced. This value can be used only on a form that was generated via Lasso (post-Lasso) and is determined by the layout specified on the previous action. The value could simply be displayed, or entered into a field, for example a log database that records Lasso activity. Or, it could be used in a conditional statement to determine the HTML output. Display List ValuesC Sub-ContainerD [list_value] The [list_value] tag will return the value list items that are currently defined in the FileMaker Pro database, for the field specified by the [value_list: ] tag. It can only be used with the [value_list: [/value_list] container tag. All items will be returned unless the checked selected parameter is used to indicate that only the selected items for a specific record be shown. For more details, see Value Lists. CJ^Returns all value list items for the field specified using the [value_list:...] container tag.L [list_value]N]Only valid within the [value_list:...] [/value_list] container. Accepts encoding parameters.O [FMP-ValueListItem]PV[value_list:"YourFieldName"] [if: checked != ""][else][list_value],[/if] [/value_list] [value_list:"YourFieldName"] [if: checked != ""][else][list_value],[/if] [/value_list] The [list_value] tag will return the value list items that are currently defined in the FileMaker Pro database, for the field specified by the [value_list: ] tag. It can only be used with the [value_list: [/value_list] container tag. All items will be returned unless the checked selected parameter is used to indicate that only the selected items for a specific record be shown. For more detailB s, see Value Lists. Log ActivityC ContainerD [log: ...]E [/log] The [log: ] tag allows information about the current Lasso action to either be written to a text file or displayed in the server (or Lasso.acgi) log window. Lasso will log whatever is between the opening and closing [log: ] tags at idle time, including any values from Lasso substitution tags. Use a line break at the end of the line to have each log entry to appear on its own line in the log file. If a path is indicated, the values specified between the [log: [/log] container are add ed to the end of the file indicated. The path must be indicated from the root level of the Web-serving folder. If a path and file is not specified, a default log file, Lasso.log, will be created at the root level of the server. Using window outputs the text or tags in between the opening and closing [log: ] tags to the Lasso log window instead of a file. For example: [log: window]no result:[server_date,short], [server_time,short],[database_name],[form_param: category"], [formpara m:"name"],[client_username] The logged information cannot be stored in a database; however an inline action can be used to accomplish that. JuAllows information about the current Lasso action to either be written to a text file or displayed in the log window.L [log: ...] ... [/log]N[The path and file of log or the "window" parameter. Within container: what is to be logged.P>[log: "/Path/to/LogFile"] ...the log text or lasso tags [/log] [log: "/Path/to/LogFile"] ...the log text or lasso tags [/log] The [log: ] tag allows information about the current Lasso action to either be written to a text file or displayed in the server (or Lasso.acgi) log window. Lasso will log whatever is between the opening and closing [log: ] tags at idle time, including any values from Lasso substitution tags. Use a line break at the end of the line to have each log entry to appear on its own line in the log file. If a path is indicated, the values specified between the [log: [/log] container are added to the end of the file indicated. The path must be indicated from the root level of the Web-serving folder. If a path and file is not specified, a default log file, Lasso.log, will be created at the root level of the server. Using window outputs the text or tags in between the opening and closing [log: ] tags to the Lasso log window instead of a file. For example: [log: window]no result:[server_date,short], [serverC _time,short],[database_name],[form_param: category"], [formparam:"name"],[client_username] The logged information cannot be stored in a database; however an inline action can be used to accomplish that. Logical OperatorC CommandD -logicalop Use the -logicalop command tag to select an operator ("and or") to search by. A logical operator can be used to determine whether the search criteria will find: Records that fulfill all the parameters indicated (this would be an type search) Records in which any one (or more) of the parameters indicated are valid (this would be an type search). The logical operator applies to all search fields on the form. If no operator is indicated, the default logical operator is and." This can also be coded as a hidden input type. For example, to specify type searching, enter: <input type="hidden name="-logicalop value="or"> Currently, a single logical operator affects all fields globally. Field-level operators can be applied by enclosing fields within the -opbegin and -opend tags. The value of this tag can be returned to the reply page using the [logicalop_value] tag. J1Selects an operator ("and" or "or") to search by.L -logicalopO <input type="radio" name="-logicalop" value="Find Records that Match All (and) " checked>and <input type="radio" name="-logicalop" value="Find Records that Match Any (or)">or <input type="radio" name="-logicalop" value="Find Records that Match All (and) " checked>and <input type="radio" name="-logicalop" value="Find Records that Match Any (or)">or Use the -logicalop command tag to select an operator ("and or") to search by. A logical operator can be used to determine whether the search criteria will find: Records that fulfill all the parameters indicated (this would be an type search) Records in which any one (or more) of the parameters indica ted are valid (this would be an type search). The logical operator applies to all search fields on the form. If no operator is indicated, the default logical operator is and." This can also be coded as a hidden input type. For example, to specify type searching, enter: <input type="hidden name="-logicalop value="or"> Currently, a single logical operator affects all fields globally. Field-level operators can be applied by enclosing fields within the -opbegin and -opend taC]gs. The value of this tag can be returned to the reply page using the [logicalop_value] tag. Display Logical OperatorC SubstitutionD [logicalop_value]I The [logicalop_value] tag is used to display the parameters used on the previous search (typically on the hitlist return page). [logicalop_value] will be substituted with based on the logical operator specified in the original search.JUSubstitutes the parameters used on the previous search into the page being processed [logicalop_value]N Accepts encoding parameters.O [FMP-CurrentLOP]P [logicalop_value] [logicalop_value] The [logicalop_value] tag is used to display the parameters used on the previous search (typically on the hitlist return page). [logicalop_value] will be substituted with based on the logical operator specified in the original search. LoopC ContainerD [loop: ...]E [/loop] The [loop: ][/loop] tag instructs Lasso to display all HTML or tags between the opening and closing [loop] tags the specified number of times. A number parameter is used to indicate the number of times it will loop, this can be a literal number or the result of another Lasso tag. The [loop: ] tag has limited functionality when used on its own to repeatedly display some text a specified number of times. However, it has greater functionality when combined with other tags to add looping fun ctionality to those tags. Here is one example of the [loop: ] tag when used with the [field_name: ] tag. In this example, an inline is used to retrieve the names of all fields in the specified database: [inline: database="Employees.fp3", layout="Detail", show] About to loop [field_name: count] times [loop: (field_name:count)] [field_name: loop_count][if: loop_count != field_name: count], [/if] [/loop] [/inline] The result of this tag could be, as an example: About to loop 30 times First Name, Last Name, Social Security Number, Street, City, State, Zip, Home Phone, Employee Number, Shift, Next Month Shift, Hire Date, Group, Comments, Nice Traits, Email, Home Page, Favorite Colored Dot, Edit Date, Edit Time, Photo, employee_id, total_expense, image_present, test, expenselist::expense_id, expenselist::date, expenselist::amount, expenselist::description, expenselist::expense_category Note the (field_name:count) tag is used for determining the number of times t Dche looping should occur. The count parameter evaluates to the total number of fields on a layout. J5Displays contained items a specified number of times.L [loop: ...] ... [/loop]N?Number of loops, within the container: what should be repeatedO&[FMP-LayoutFields] [/FMP-LayoutFields]P.[loop: number] ...any text or tags... [/loop] [loop: number] ...any text or tags... [/loop] The [loop: ][/loop] tag instructs Lasso to display all HTML or tags between the opening and closing [loop] tags the specified number of times. A number parameter is used to indicate the number of times it will loop, this can be a literal number or the result of another Lasso tag. The [loop: ] tag has limited functionality when used on its own to repeatedly display some text a specified number of times. However, it has greater functionality when combined with other tags to add looping functionality to those tags. Here is one example of the [loop: ] tag when used with the [field_name: ] tag. In this example, an inline is used to retrieve the names of all fields in the specified database: [inline: database="Employees.fp3", layout="Detail", show] About to loop [field_name: count] times [loop: (field_name:count)] [field_name: loop_count][if: loop_count != field_name: count], [/if] [/loop] [/inline] The result of thi s tag could be, as an example: About to loop 30 times First Name, Last Name, Social Security Number, Street, City, State, Zip, Home Phone, Employee Number, Shift, Next Month Shift, Hire Date, Group, Comments, Nice Traits, Email, Home Page, Favorite Colored Dot, Edit Date, Edit Time, Photo, employee_id, total_expense, image_present, test, expenselist::expense_id, expenselist::date, expenselist::amount, expenselist::description, expenselist::expense_category Note the (field_name:count) t ag is used for determining the number of times the looping should occur. The count parameter evaluates to the total number of fields on a layout. Loop CountC Sub-ContainerD [loop_count] The [loop_count] tag outputs a number representing the current repeat of a container tag such as record, value_list, loop, repeating, search args, sort args, or portal. For example, in a portal the first record in the portal would have a loop count of 1, the second 2, the third 3, and so on. The value is useful for use in conditionals to display the repetition value. For example, it can simply be used with the [loop: ] tag: [loop: 10] This is loop # [loop_count]. [/loop] To show all r epeat values in a numbered list: [repeating:"YourFieldName"] [loop_count]) [repeat_value]<BR CLEAR=ALL> [/repeating] Or, to number the rows of a portal: [portal:JOBS] ROW #: [loop_count][field:"JOBS::CONTACTS"]<BR> [/portal] loop_count value can be used in conditional statements. Here is a simple example: [loop: number] [if: loop_count==5] This is the fifth time in the loop [/loop] Or, the following can be used to display the first five repeats of a repeating field: [repeat ing:test] [if: loop_count <= 5] <input type="text size=30 name="test value="[repeat_value]"><br> [/if] [/repeating] Or to only display the first sort arguments used on the previous search: [sort_args] [if: loop_count == 1][sort_field][sort_order][/if] [/sort_args] Outputs the number of the current repeat of containers such as record, value_list, loop, repeating, search args, sort args, or portal. L [loop_count] HNHOnly valid within repeating container tags. Accepts encoding parameters.P [loop_count] [loop_count] The [loop_count] tag outputs a number representing the current repeat of a container tag such as record, value_list, loop, repeating, search args, sort args, or portal. For example, in a portal the first record in the portal would have a loop count of 1, the second 2, the third 3, and so on. The value is useful for use in conditionals to display the repetition value. For example, it can simply be used with the [loop: ] tag: [loop: 10] This is loop # [loop_count]. [/loop] To show all repeat values in a numbered list: [repeating:"YourFieldName"] [loop_count]) [repeat_value]<BR CLEAR=ALL> [/repeating] Or, to number the rows of a portal: [portal:JOBS] ROW #: [loop_count][field:"JOBS::CONTACTS"]<BR> [/portal] loop_count value can be used in conditional statements. Here is a simple example: [loop: number] [if: loop_count==5] This is the fifth time in the loop [/loop] Or, the following can be used to display the first five repeats of a repeating f ield: [repeating:test] [if: loop_count <= 5] <input type="text size=30 name="test value="[repeat_value]"><br> [/if] [/repeating] Or to only display the first sort arguments used on the previous search: [sort_args] [if: loop_count == 1][sort_field][sort_order][/if] [/sort_args] Math-AddC SubstitutionD [math-add: ...] The [math-add: ] tag is used to add a list of values. Each value must be a number or any Lasso tag that is substituted as a number. Each value is separated by a comma. For example (equivalent to: the current value of the field price + 6.3, when the value of price is 20): [math-add: field:"price", 6.3] Output: 26.3 Another example (equivalent to: 2 + 2 + 14 + 3): [math-add: 2, 2, 14, 3] Output: 21 Another example (equivalent to: 5 + 3.3 + 20.12 + 1): [math-add: 5, 3.3, 2B 0.12, 1] Output: 29.42 Adds a list of values.L [math-add: ...]N0numbers or a Lasso tag that results in a numberP [math-add: ...] [math-add: ...] The [math-add: ] tag is used to add a list of values. Each value must be a number or any Lasso tag that is substituted as a number. Each value is separated by a comma. For example (equivalent to: the current value of the field price + 6.3, when the value of price is 20): [math-add: field:"price", 6.3] Output: 26.3 Another example (equivalent to: 2 + 2 + 14 + 3): [math-add: 2, 2, 14, 3] Output: 21 Another example (equivalent to: 5 + 3.3 + 20.12 + 1): [mB)ath-add: 5, 3.3, 20.12, 1] Output: 29.42 Math-DivideC SubstitutionD [math-div: ...] The [math-div: ] tag is used to divide a list of values. The specified values will be divided in the order in which they appear in the string. Each value is separated by a comma. Each value must be a number, or any Lasso tag that is substituted as a number. The result is rounded to the precision used in the values. For example (equivalent to: 25/ 5/ 2): [math-div: 25, 5, 2] Output: 3 For example (equivalent to: 25.0/ 5/ 2): [math-div: 25.0, 5, 2] Output: 2.5 Divides a list of values.L [math-div: ...]N0numbers or a Lasso tag that results in a numberP [math-div: ...] [math-div: ...] The [math-div: ] tag is used to divide a list of values. The specified values will be divided in the order in which they appear in the string. Each value is separated by a comma. Each value must be a number, or any Lasso tag that is substituted as a number. The result is rounded to the precision used in the values. For example (equivalent to: 25/ 5/ 2): [math-div: 25, 5, 2] Output: 3 For example (equivalent to: 25.0/ 5/ 2): [math-div: 25.0, 5, 2] Output: 2.5 Math-ModuloC SubstitutionD [math-mod: ...] The [math-mod: ] tag is used to divide two values and output the remainder of that division. The remainder is also referred to as the modulo. The specified values will be divided in the order in which they appear in the string. Each value is separated by a comma. Each value must be a number, or any Lasso tag that is substituted as a number. For example (equivalent to: 43/ 10 = 4 with a remainder of 3): [math-mod: 43, 10] Output: 3 Another example (equivalent to: 29.50/ 5 = with a B7remainder of 4.5): [math-mod: 29.50, 5] Output: 4.5 J,Outputs the remainder of a divide operation.L [math-mod: ...]N0numbers or a Lasso tag that results in a numberP [math-mod: ...] [math-mod: ...] The [math-mod: ] tag is used to divide two values and output the remainder of that division. The remainder is also referred to as the modulo. The specified values will be divided in the order in which they appear in the string. Each value is separated by a comma. Each value must be a number, or any Lasso tag that is substituted as a number. For example (equivalent to: 43/ 10 = 4 with a remainder of 3): [math-mod: 43, 10] Output: 3 Another example (equivalent to: BI29.50/ 5 = with a remainder of 4.5): [math-mod: 29.50, 5] Output: 4.5 Math-MultiplyC SubstitutionD [math-mult: ...] The [math-mult: ] tag is used to multiply a list of values together. Each value is separated by a comma. Each value must be number, or any Lasso tag that is substituted as a number. The result is rounded to the precision used in the values. For example (equivalent to: 5 * 5 * 14 * 2): [math-mult: 5, 5, 14, 2] Output: 700 Another example (equivalent to: the current value of the field price * 6.3, when the value of price is 20): [math-mult: field:"price", 6.3] Output: 126.0 Another example (equivalent to: 25.0 * 5 * 2): [math-mult: 25.0, 5, 2] Output: 250.0 More complicated expressions can be created by separating the elements of the calculations by parenthesis. For example (meaning 2 + 2 * 6 / 4 - 2): [[math-sub: (math-add: 2, (math-div: (math-mult: 2, 6), 4)), 2] Output: 3 Multiplies a list of values.L [math-mult: ...]N0numbers or a Lasso tag that results in a numberP [math-mult: ...] [math-mult: ...] The [math-mult: ] tag is used to multiply a list of values together. Each value is separated by a comma. Each value must be number, or any Lasso tag that is substituted as a number. The result is rounded to the precision used in the values. For example (equivalent to: 5 * 5 * 14 * 2): [math-mult: 5, 5, 14, 2] Output: 700 Another example (equivalent to: the current value of the field price * 6.3, when the value of price is 20): [math-mult: field:"price", 6 Output: 126.0 Another example (equivalent to: 25.0 * 5 * 2): [math-mult: 25.0, 5, 2] Output: 250.0 More complicated expressions can be created by separating the elements of the calculations by parenthesis. For example (meaning 2 + 2 * 6 / 4 - 2): [[math-sub: (math-add: 2, (math-div: (math-mult: 2, 6), 4)), 2] Output: 3 Math-Round ResultC SubstitutionD [math-round: ...] The [math-round: ] tag is used to round a value to the nearest value. Only one value can be evaluated with one [math-round] tag. A number parameter can be used to specify the precision of the rounded result. The number of decimal places to be used is indicated by the tenth power, i.e., 100, 10, 1, .01, .001, and so on. The number parameter is separated from the value by a comma. The value to be rounded must be a number, or any Lasso tag that results in a number. For example (equivalent to: 1345.75 rounded to the nearest 1) : [math-round: 1345.75, 1] Output: 1346 Another example (equivalent to: 1345.75 rounded to the nearest 0.1) : [math-round: 1345.75, .1] Output: 1345.8 Another example (equivalent to: 1355.1234 rounded to the nearest 0.01) : [math-round: 1355.1234, .01] Output: 1355.12 Another example (equivalent to: 1345.12354 rounded to the nearest 0.001) : [math-round: 1345.12354, .001] Output: 1345.124 J$Rounds a value to the nearest value. [math-round: ...]N0numbers or a Lasso tag that results in a numberP [math-round: ...] [math-round: ...] The [math-round: ] tag is used to round a value to the nearest value. Only one value can be evaluated with one [math-round] tag. A number parameter can be used to specify the precision of the rounded result. The number of decimal places to be used is indicated by the tenth power, i.e., 100, 10, 1, .01, .001, and so on. The number parameter is separated from the value by a comma. The value to be rounded must be a number, or any Lasso tag that results in a number. For e xample (equivalent to: 1345.75 rounded to the nearest 1) : [math-round: 1345.75, 1] Output: 1346 Another example (equivalent to: 1345.75 rounded to the nearest 0.1) : [math-round: 1345.75, .1] Output: 1345.8 Another example (equivalent to: 1355.1234 rounded to the nearest 0.01) : [math-round: 1355.1234, .01] Output: 1355.12 Another example (equivalent to: 1345.12354 rounded to the nearest 0.001) : [math-round: 1345.12354, .001] Output: 1345.124 Math-SubtractC SubstitutionD [math-sub: ...] The [math-sub: ] tag is used to subtract a list of values. The specified values are subtracted in the order in which they appear in the string. Each value must be a number, or any Lasso tag that is substituted as a number. Each value is separated by a comma. For example (equivalent to: the current value of the field price - 6.3, when the value of price is 20): [math-sub: field:"price", 6.3] Output: 13.7 Another example (equivalent to: 5 - 3 - 20 - 1): [math-sub: 5, 3, 20, 1 Output: -19 Another example (equivalent to: 5 - 3.3 - 20.12 - 1): [math-sub: 5, 3.3, 20.12, 1] Output: -19.42 More complicated expressions can be created by separating the elements of the calculations by parentheses. For example (equivalent to: 2 + 2 * 6 / 4 - 2): [[math-sub: (math-add: 2, (math-div: (math-mult: 2, 6), 4)), 2] Output: 3 Subtracts a list of values.L [math-sub: ...]N0numbers or a Lasso tag that results in a numberP [math-sub: ...] [math-sub: ...] The [math-sub: ] tag is used to subtract a list of values. The specified values are subtracted in the order in which they appear in the string. Each value must be a number, or any Lasso tag that is substituted as a number. Each value is separated by a comma. For example (equivalent to: the current value of the field price - 6.3, when the value of price is 20): [math-sub: field:"price", 6.3] Output: 13.7 Another example (equivalent to: 5 - 3 - 20 - 1): [math n-sub: 5, 3, 20, 1] Output: -19 Another example (equivalent to: 5 - 3.3 - 20.12 - 1): [math-sub: 5, 3.3, 20.12, 1] Output: -19.42 More complicated expressions can be created by separating the elements of the calculations by parentheses. For example (equivalent to: 2 + 2 * 6 / 4 - 2): [[math-sub: (math-add: 2, (math-div: (math-mult: 2, 6), 4)), 2] Output: 3 Maximum RecordsC CommandD -maxrecords The -maxRecords tag limits the maximum number of records returned on the hitlist page. Lasso uses a default maximum of 50 records returned per page. Specifying tells Lasso to return all records for a specific search, e.g.: <input type="hidden name="-maxRecords value="all"> Specifying does not mean that all records in the database would be found. The -findall tag can be used to accomplish that. There is no limit imposed by Lasso on the number of records that can be returne d. However, the formatted HTML page returned to the user is limited by the amount of memory allocated to Lasso; the default is around 72K bytes. Normally, that would allow about 200 records from the sample Employees database to be returned. Also, as the number of returned records goes up, the performance goes down. It gives your user a perception of faster performance by returning a subset of returned records, and using [next] links to view successive pages. The 72K byte limit can be increased by increasing the memory partition in the Get Info box for Lasso.acgi. Half of all memory greater than the preferred setting is allocated to the HTML output file. That is, if you increase the Lasso memory partition by 100K bytes, the size of the HTML output file increases to 122K bytes (72K + 50K). The value of this tag can be returned to the reply page using the [maxRecords_value] tag. JCLimits the maximum number of records displayed on the hitlist page.L -maxrecordsO -MaxP}<select name="-maxrecords" size=1> <option>5 <option selected>10 <option>20 <option>30 <option>50 <option>all </select> <select name="-maxrecords" size=1> <option>5 <option selected>10 <option>20 <option>30 <option>50 <option>all </select> The -maxRecords tag limits the maximum number of records returned on the hitlist page. Lasso uses a default maximum of 50 records returned per page. Specifying tells Lasso to return all records for a specific search, e.g.: <input type="hidden name="-maxRecords value="all"> Specifying does not mean that all records in the database would be found. Th e -findall tag can be used to accomplish that. There is no limit imposed by Lasso on the number of records that can be returned. However, the formatted HTML page returned to the user is limited by the amount of memory allocated to Lasso; the default is around 72K bytes. Normally, that would allow about 200 records from the sample Employees database to be returned. Also, as the number of returned records goes up, the performance goes down. It gives your user a perception of faster performa nce by returning a subset of returned records, and using [next] links to view successive pages. The 72K byte limit can be increased by increasing the memory partition in the Get Info box for Lasso.acgi. Half of all memory greater than the preferred setting is allocated to the HTML output file. That is, if you increase the Lasso memory partition by 100K bytes, the size of the HTML output file increases to 122K bytes (72K + 50K). The value of this tag can be returned to the reply pagD#e using the [maxRecords_value] tag. Display Maximum Records ValueC SubstitutionD [maxrecords_value] MThe [maxrecords_value] tag is used to display the parameters used on the previous search (typically on the hitlist return page). [maxrecords_value] will be substituted with a number representing the total records to be included in a group. The maxrecords value is specified with the original search form or URL (the default is 50). PJcSubsitutes the number of maximum number of records to be used in a subset of a found set of recordsL [maxrecords_value]N Accepts encoding parameters.O [FMP-CurrentMax]P [maxrecords_value] a[maxrecords_value] The [maxrecords_value] tag is used to display the parameters used on the previous search (typically on the hitlist return page). [maxrecords_value] will be substituted with a number representing the total records to be included in a group. The maxrecords value is specified with the original search form or URL (the default is 50). Next Record GroupC ContainerD [next]E [/next]I8Refer to the notes for the [prev] tag for a description.J4Displays the next group of the found set of records.L [next] ... [/next]N9Within container: the text to display for the "Next" linkO [FMP-LinkNext] [/FMP-LinkNext]P%[next] Next Group of Records [/next]Q_[next] Next Group of Records [/next] Refer to the notes for the [prev] tag for a description. Display Next URLC Substitution [next_url] The [next_url] and [prev_url] tags are used to display the links created with the [next] [/next] and [prev] [/prev] tags. These links are used for linking to the previous or next group of records when a set of records is returned in groups. They are useful when troubleshooting, or when creating manual links that function similarly to the [next] and [prev] tags. The result can also be used in a conditional statement. J3Display the next link created with the [next] tag. L [next_url]N Accepts encoding parameters.PM<p>This is the next link: [next_url] <p>This is the previous link: [prev_url] <p>This is the next link: [next_url] <p>This is the previous link: [prev_url] The [next_url] and [prev_url] tags are used to display the links created with the [next] [/next] and [prev] [/prev] tags. These links are used for linking to the previous or next group of records when a set of records is returned in groups. They are useful when troubleshooting, or when creating manual links that function similarly to the [next] and [prev] tags. The result can also be used in a conditional statB ement. Number Records FoundC SubstitutionD [nfound] The substitution tag [nFound] is used when displaying the numeric range of a found set of records. The [nFound] value is the total number of records found. Here is one example of how to format this tag with the others substitution tags used for displaying the range of a found set of records: <p>Displaying records <b>[begNum]</b> thru <b>[endNum]</b> (<b>[nShown]</b> records displayed).<br> (<b>[nFound]</b> records found out of <b>[total_records]</b> in database) J+Displays the total number of records found.L [nfound]N Accepts encoding parameters.O [FMP-CurrentFoundCount]P [nfound] [nfound] The substitution tag [nFound] is used when displaying the numeric range of a found set of records. The [nFound] value is the total number of records found. Here is one example of how to format this tag with the others substitution tags used for displaying the range of a found set of records: <p>Displaying records <b>[begNum]</b> thru <b>[endNum]</b> (<b>[nShown]</b> records displayed).<br> (<b>[nFound]</b> records found out of <b>[total_records]</b> in database) No Results ReplyC CommandD -noresultsI The -noresults tag delivers the specified file when no results are found, that is, when a search fails to find any records that match the specified search parameters. J4Delivers a specified file when no results are found.L -noresultsO -Error (plus a workaround)PH<input type="hidden" name="-noresults" value="Pathto/YourFileName.html"> <input type="hidden" name="-noresults" value="Pathto/YourFileName.html"> The -noresults tag delivers the specified file when no results are found, that is, when a search fails to find any records that match the specified search parameters. NothingC ActionD -nothing The -nothing action instructs Lasso to process a file but not act upon any database. It is the default action that is used if no action is specified. The -nothing action will process any tags on the reply page such as any server-side includes or inline actions. It can be used to create a button to submit a form that is not directed to a database as follows: <input type="submit name="-nothing value="Submit"> The -nothing action does not need to be specified, but provides consistency in < how tags are used. Only the response file must be specified, that is, there is no need to specify a database and layout with this action. However, other tags such as email tags can be specified within the action. The -nothing action will not populate value lists or gather any data from the FileMaker Pro database. J@Instructs Lasso to process a file but not act upon any database.L -nothingPU<a href="action.lasso?-nothing&-response=Pathto/YourFileName.html">Activate Lasso</a> <a href="action.lasso?-nothing&-response=Pathto/YourFileName.html">Activate Lasso</a> The -nothing action instructs Lasso to process a file but not act upon any database. It is the default action that is used if no action is specified. The -nothing action will process any tags on the reply page such as any server-side includes or inline actions. It can be used to create a button to submit a form that is not directed to a database as follows: <input type="submit name="-nothing value="S ubmit"> The -nothing action does not need to be specified, but provides consistency in how tags are used. Only the response file must be specified, that is, there is no need to specify a database and layout with this action. However, other tags such as email tags can be specified within the action. The -nothing action will not populate value lists or gather any data from the FileMaker Pro database. Number Record ShownC SubstitutionD [nshown] .The substitution tag [nShown] is used when displaying the range in a found set of records, in this case, the total number of records being displayed in a subset of returned records. If all records are returned in the same group, then the value of [nShown] is the same as the number of records returned. JEDisplays the total number of records in a subset of returned records.L [nshown]O [FMP-RangeSize]P [nshown] 8[nshown] The substitution tag [nShown] is used when displaying the range in a found set of records, in this case, the total number of records being displayed in a subset of returned records. If all records are returned in the same group, then the value of [nShown] is the same as the number of records returned. Begin Logical OperatorC CommandD -opbegin The -opbegin and -opend command tags can be used to create a field-level operator, or multiple field-level operators. Any fields specified between the -opbegin and -opend tags on a search form will be grouped under the specified logical operator. The value of this tag can be The default is There must be one -opend tag for every -opbegin tag. The -opend tag does not need to specify any value. logical operator can be applied only to one subsequent it em to indicate that the value entered should not be used on a search. The item can be either a search field, or another -opbegin tag which can group other search fields or -opbegin tags. For example: <input type="hidden name="-opbegin value="not"> <input type="hidden name="-opbegin value="and"> Do not include Names: <input type="text name="name size="30"> Do not include Dates: <input type="text name="date size="30"> <input type="hidden name="-opend"> <input type="hidden {me="-opend"> If one of these values is not included it won t be used with the logical operator. If the [search_args] [/search_args] tags are used on the reply page, then the no_ops parameter should be used as follows: [search_args,no_ops] [/search_args] The current field-level logical operators will not be displayed along with the other fields used in the search. J'Creates a field-level logical operator.L -opbegin <input type="hidden" name="-opbegin" value="or"> ...insert fields to use this logical operator here... <input type="hidden" name="-opend"> <input type="hidden" name="-opbegin" value="or"> ...insert fields to use this logical operator here... <input type="hidden" name="-opend"> The -opbegin and -opend command tags can be used to create a field-level operator, or multiple field-level operators. Any fields specified between the -opbegin and -opend tags on a search form will be grouped under the specified logical operator. The value of this tag can be The default is There must be one -opend tag for every -opbegin tag. The -opend tag does not need to specify any value. logical operator can be applied only to one subsequent item to indicate that the value entered should not be used on a search. The item can be either a search field, or another -opbegin tag which can group other search fields or -opbegin tags. For example: <input type="hidden name="-opbegin value="not"> <input type="hidden name="-opbegin value="and"> Do not include Names: <input type="text name="na size="30"> Do not include Dates: <input type="text name="date size="30"> <input type="hidden name="-opend"> <input type="hidden name="-opend"> If one of these values is not included it won t be used with the logical operator. If the [search_args] [/search_args] tags are used on the reply page, then the no_ops parameter should be used as follows: [search_args,no_ops] [/search_args] The current field-level logical operators will not be displayed along with the other fields used in the search. End Logical OperatorC CommandD -opendI The -opend tag ends the field-level operator. There must be one -opend tag for every -opbegin tag. Refer to the description for the -opbegin tag for more details.J Ends a field-level operator.L -opendP <input type="hidden" name="-opbegin" value="or"> ...insert fields to use this logical operator here... <input type="hidden" name="-opend"> /<input type="hidden" name="-opbegin" value="or"> ...insert fields to use this logical operator here... <input type="hidden" name="-opend"> The -opend tag ends the field-level operator. There must be one -opend tag for every -opbegin tag. Refer to the description for the -opbegin tag for more details. OperatorC CommandD -operator The -operator command tag determines how Lasso will compare the entered value with field values to find matches. The abbreviation -op can also be used. The search operator value must be one of the search operators supported by Lasso. The following operators can be used: eq (equals), neq (not equals), cn (contains), , ew (ends with), gt (greater than), gte (greater than or equals), lt (less than), lte (less than or equals), and the default, bw (begins with). Some additional notes on operat The -operator tag affects only the search field that immediately follows. It defaults back to begins with after that search field. The contains operator evaluates all character sequences, thus slowing completion of the search. Different operators are more appropriate for different types of fields. The sample syntax shows the operators that are appropriate for text searches. For number fields the following operator choices make the most sense: <select name="-op"> <optio n value="eq selected> = <option value="gt"> > <option value="gte"> > or = <option value="lt"> < <option value="lte"> < or = <option value="cn"> contains <option value="bw"> begins with <option value="ew"> ends with </select> <input type=text size=30 name="YourFieldName"> Note: Greater than or less than symbols need to be encoded as > and < If a field is defined as a date or time type field, then you must specify an operator that is either equals, ater than, greater than or equals, less than, less than or equals. The value of the -operator tag can be returned to the reply page using the [search_args] [search_op] [/search_args] container tag (along with the search field and value using [search_field] and[search_value]). The operator can be hard-coded to predetermine how the search is carried out. For example: <input type="hidden name="-operator value="equals"> YJVDetermines how Lasso will compare the entered value with field values to find matches.L -operatorO <select name="-op"> <option value="bw" selected> <option value="eq">equals <option value="cn" >contains <option value="ew">ends with </select> <input type=text size=30 name="YourFieldName"> <select name="-op"> <option value="bw" selected> <option value="eq">equals <option value="cn" >contains <option value="ew">ends with </select> <input type=text size=30 name="YourFieldName"> The -operator command tag determines how Lasso will compare the entered value with field values to find matches. The abbreviation -op can also be used. The search operator value must be one of the search operators supported by Lasso. The following operators can be used: eq (equals), neq (not equals), cn (contains), , ew (ends with), gt (greater than), gte (greater than or equals), lt (less than), lte (less than or equals), and the default, bw (begins with). Some additional notes on operators: The -operator tag affects only the search field that immediately follows. It defaults back to begins with after that search field. The contains operator evaluates all character sequences, thus slowing completion of the search. Different operators are more appropriate for di fferent types of fields. The sample syntax shows the operators that are appropriate for text searches. For number fields the following operator choices make the most sense: <select name="-op"> <option value="eq selected> = <option value="gt"> > <option value="gte"> > or = <option value="lt"> < <option value="lte"> < or = <option value="cn"> contains <option value="bw"> begins with <option value="ew"> ends with </select> <input type=text size=30 name="YourFieldN ame"> Note: Greater than or less than symbols need to be encoded as > and < If a field is defined as a date or time type field, then you must specify an operator that is either equals, greater than, greater than or equals, less than, less than or equals. The value of the -operator tag can be returned to the reply page using the [search_args] [search_op] [/search_args] container tag (along with the search field and value using [search_field] and[search_value]). The operator can be hard-coded to predetermine how the search is carried out. For example: <input type="hidden name="-operator value="equals"> Options in Selection ListC SubstitutionD [option: ...] The [option: ] tag can be used to format fields that contain value lists as HTML pop-up or pull-down menus on a post-Lasso format file. To have Lasso retrieve a value list for a field, that field must be formatted to include a value list on the specified database and layout. For every value in the value list, Lasso will create an HTML option in the form: <option>List Value OR <option selected>List Value In other words, Lasso simply grabs the current value list and places the HTML opti on tag before the value. In addition, the HTML selected parameter is automatically added by Lasso if the list value is checked in the database. For example, if the following is used on a post-Lasso file: <select name="YourFieldName"> [option:"YourFieldName"] </select> Lasso will process the [option: ] tag, and output the above as HTML as follows: <select name="YourFieldName size=1> <option>value1 <option>value2 <option>value3 </select> As is shown in the sample syntax, an addit ional blank option can be included so that the first choice on the list is blank (that is, the default choice will have nothing selected, and nothing will be used if it is selected). Alternatively, pop-up lists can also be created with the [value_list: ] tag as follows: <select name="YourFieldName"> <option> [value_list:"YourFieldName"] <option value="[list_value] [selected]>[list_value] [/value_list] </select> Conditionals can be used to not include certain list value items. Fo r example, when using a separator in your value list (a hypen is used as an item on the list), the following can be used: <input type="hidden name="[required]"> <select name="YourFieldName"> [value_list: YourFieldName"] [If: list_value=="-"] <option value="">[list_value] [else] <option value="[list_value] [selected]>[list_value] [/if] [/value_list] </select> The hypen is entered as a null value. Since the required tag is used, if the separator hyphen is selected, the f orm cannot be submitted. JHUpdates fields with a pop-up selection list on a post-Lasso format file.L [option: ...]N/Name of the field. Accepts encoding parameters.O [FMP-Option: ...]Pj<select name="YourFieldName"> <option value=""> --- Make a Selection --- option:YourFieldName] </select> <select name="YourFieldName"> <option value=""> --- Make a Selection --- option:YourFieldName] </select> The [option: ] tag can be used to format fields that contain value lists as HTML pop-up or pull-down menus on a post-Lasso format file. To have Lasso retrieve a value list for a field, that field must be formatted to include a value list on the specified database and layout. For every value in the value list, Lasso will create an HTML option in the form: <option>List Value OR <op tion selected>List Value In other words, Lasso simply grabs the current value list and places the HTML option tag before the value. In addition, the HTML selected parameter is automatically added by Lasso if the list value is checked in the database. For example, if the following is used on a post-Lasso file: <select name="YourFieldName"> [option:"YourFieldName"] </select> Lasso will process the [option: ] tag, and output the above as HTML as follows: <select name="YourFieldName ize=1> <option>value1 <option>value2 <option>value3 </select> As is shown in the sample syntax, an additional blank option can be included so that the first choice on the list is blank (that is, the default choice will have nothing selected, and nothing will be used if it is selected). Alternatively, pop-up lists can also be created with the [value_list: ] tag as follows: <select name="YourFieldName"> <option> [value_list:"YourFieldName"] <option value="[list_value] [selected]> [list_value] [/value_list] </select> Conditionals can be used to not include certain list value items. For example, when using a separator in your value list (a hypen is used as an item on the list), the following can be used: <input type="hidden name="[required]"> <select name="YourFieldName"> [value_list: YourFieldName"] [If: list_value=="-"] <option value="">[list_value] [else] <option value="[list_value] [selected]>[list_value] [/if] [/value_list] </select> The hyE pen is entered as a null value. Since the required tag is used, if the separator hyphen is selected, the form cannot be submitted. PortalC ContainerD [portal: ...]E [/portal] The [portal] [/portal] tag pair will display multiple rows of a portal located on a specific FileMaker Pro database layout. Each portal row represents a related record, and only those fields contained in the row can be added, displayed, or updated. The opening [portal] tag must specify the name of the FileMaker Pro relationship. Related fields must be fully specified as: RelationshipName::Field Name Lasso will loop through the rows in the portal and display everything between the open ing and closing [portal] tags for each record in the portal. Several field references (from the same relationship) can be displayed within the [portal] tags, as in the following example: [portal: TRAVEL] <hr><b>Cities:</b> [Cities: TRAVEL::Cities]<br> <b>Countries:</b> [Countries: TRAVEL::Countries]<br> <b>Airlines:</b> [Airlines: TRAVEL::Airlines]<br> [/portal] Only related fields of the relationship specified in the [portal] tag can appear between the [portal] [/portal] tag pair. If a portal uses a vertical scroll bar on the referenced FileMaker Pro layout, then all related records (rows) are returned. Otherwise, the number of rows returned equals the number of rows defined in the Portal Setup dialog under Show _ rows where the underscore represents the number of rows displayed on the FileMaker Pro layout. Note: Do not place a related field in the header portion of your FileMaker Pro database layout. For some reason, this will prevent the portal from appeaD ring. J<Displays the multiple rows of a portal on a database layout.L [portal: ...] ... [/portal]NKThe name of the relationship, within container: any related fields or HTMLO [FMP-Portal: ...] [/FMP-Portal]P][portal: "YourRelationshipName"] [field:"YourRelationshipName::YourFieldName"]<br> [/portal] [portal: "YourRelationshipName"] [field:"YourRelationshipName::YourFieldName"]<br> [/portal] The [portal] [/portal] tag pair will display multiple rows of a portal located on a specific FileMaker Pro database layout. Each portal row represents a related record, and only those fields contained in the row can be added, displayed, or updated. The opening [portal] tag must specify the name of the FileMaker Pro relationship. Related fields must be fully specified as: RelationshipName::Fie ld Name Lasso will loop through the rows in the portal and display everything between the opening and closing [portal] tags for each record in the portal. Several field references (from the same relationship) can be displayed within the [portal] tags, as in the following example: [portal: TRAVEL] <hr><b>Cities:</b> [Cities: TRAVEL::Cities]<br> <b>Countries:</b> [Countries: TRAVEL::Countries]<br> <b>Airlines:</b> [Airlines: TRAVEL::Airlines]<br> [/portal] Only related fields of the re lationship specified in the [portal] tag can appear between the [portal] [/portal] tag pair. If a portal uses a vertical scroll bar on the referenced FileMaker Pro layout, then all related records (rows) are returned. Otherwise, the number of rows returned equals the number of rows defined in the Portal Setup dialog under Show _ rows where the underscore represents the number of rows displayed on the FileMaker Pro layout. Note: Do not place a related field in the header portion Ddof your FileMaker Pro database layout. For some reason, this will prevent the portal from appearing. Post-InlineC SubstitutionD [post_inline: ...] The [post_inline: ] tag allows one to execute some actions after the currently processed page is finished and returned to the user. The required post_response attribute must be included and should specify the path to the file Lasso will process. The following attributes are optional: set_hours Specify the number of hours to wait before executing the action. set_minutes Specify the number of minutes to wait before executing the action. set_day Mon[day] through Sun[day]. Sp ecify the day to execute the action. set_month 1 through 12. Specify the month to execute the action. set_time 1 through 24. Specify the hour of the day to execute the action. set_week 1 through 4. Specify the week to execute the action. Any number of named parameters can also be included as name=value pairs. These parameters can be a combination of literal text, Lasso substitution tags, or values returned from a field. For example: [post_inline: post_response="inline_lo g.txt", UserNameField"=field:"user_id", PasswordField"=field:"password","PhoneField"=field:"w_phone","DomainAddressField"=client_addr,"IPNumberField"=client_ip,"BrowserTypeField"=client_type,"LassoActionField"=lasso_action,"DatabaseNameField"=database_name] The name value pairs are included so the values can be retrieved using the [form_param: ] tag on the response page. Quotes can be optionally used to surround any literal values, including field names used with the Field tag. LassoDB tags, such as database_name should not be surrounded by quotes. The post_inline tag allows one to execute some actions after the currently processed page is finished and returned to the user. L [post_inline: ...]NMpost_response, set_hours, set_minutes, set_day, set_month, set_time, set_weekPY[post_inline: post_response="Pathto/YourFileName.html",attribute="value", "name"="value"] [post_inline: post_response="Pathto/YourFileName.html",attribute="value", "name"="value"] The [post_inline: ] tag allows one to execute some actions after the currently processed page is finished and returned to the user. The required post_response attribute must be included and should specify the path to the file Lasso will process. The following attributes are optional: set_hours Specify the number of hours to wait before executing the action. set_minutes Specify the number of minutes to wait before executing the action. set_day Mon[day] through Sun[day]. Specify the day to execute the action. set_month 1 through 12. Specify the month to execute the action. set_time 1 through 24. Specify the hour of the day to execute the action. set_week 1 through 4. Specify the week to execute the action. Any number of named parameters can also be included as name=value pairs. These parameters can be a combination of literal text, Lasso substitution tags, or values returned from a field. For example: [post_inline: post_response="inline_log.txt", UserNameField"=field:"user_id", PasswordField"=field:"password","PhoneField"=field:"w_phone","DomainAddressField"=client_addr,"IPNumberField"=client_ip,"BrowserTypeField"=client_type,"LassoActionField"=lasso_action,"DatabaseNameField"=database_name] The name value pairs are included so the values can be retrieved using the [form_param: ] tag on the response page. Quotes can be optionally D used to surround any literal values, including field names used with the Field tag. Lasso tags, such as database_name should not be surrounded by quotes. Previous Record GroupC ContainerD [prev]E [/prev] The previous and next tags allow the user to step through the found set of records a group at a time. The [prev] and [next] tags are replaced with links to display either the previous or next [nShown] group of records. The number of records in the [nShown] group is determined by the value in the -maxRecords tag (used on the search page). The appropriate search arguments that called up these records are included automatically by Lasso. As of Lasso 2.5, scripts are also included in the next and previous links. For example, if these tags are placed on a hitlist as: [next] Next page of records [/next] When a -findall action is used to call up records, the next is returned to the browser as follows: <a href="Lasso.acgi?-database=employees&-layout=summary& -response=example%2fhitlist%20format.html&-skiprecords=10& -maxRecords=10&-logicalop=and&-timeout=60&-findall"> Next page of records</a> Similarly, if the action was a search and an image is used as a sort of butt <img src="Example/next.gif border=0>[next] Next page of records [/next] Lasso will then substitute a link as: <a href="Lasso.acgi?-database=employees&-layout=summary& -response=example%2fhitlist%20format.html&-op=gte& Hire%20Date=1%2f1%2f84&-skiprecords=10&-maxRecords=10& -logicalop=and&-timeout=60&-search"> <img src="Example/next.gif border=0> Next page of records</a> J8Displays the previous group of the found set of records.L [prev] ... [/prev]N3Within container: text to appear on "Previous" linkO&[FMP-LinkPrevious] [/FMP-LinkPrevious]P5<p>[prev] Previous [/prev] [next] Next [/next] <p>[prev] Previous [/prev] [next] Next [/next] The previous and next tags allow the user to step through the found set of records a group at a time. The [prev] and [next] tags are replaced with links to display either the previous or next [nShown] group of records. The number of records in the [nShown] group is determined by the value in the -maxRecords tag (used on the search page). The appropriate search arguments that called up these records are included automatically by Lasso. As of Lasso 2.5, scripts are also included in the next and previous links. For example, if these tags are placed on a hitlist as: [next] Next page of records [/next] When a -findall action is used to call up records, the next is returned to the browser as follows: <a href="Lasso.acgi?-database=employees&-layout=summary& -response=example%2fhitlist%20format.html&-skiprecords=10& -maxRecords=10&-logicalop=and&-timeout=60&-findall"> Next page of records</a> Similarly, if the act ion was a search and an image is used as a sort of button: <img src="Example/next.gif border=0>[next] Next page of records [/next] Lasso will then substitute a link as: <a href="Lasso.acgi?-database=employees&-layout=summary& -response=example%2fhitlist%20format.html&-op=gte& Hire%20Date=1%2f1%2f84&-skiprecords=10&-maxRecords=10& -logicalop=and&-timeout=60&-search"> <img src="Example/next.gif border=0> Next page of records</a> Display Previous URLC SubstitutionD [prev_url] The [next_url] and [prev_url] tags are used to display the links created with the [next] [/next] and [prev] [/prev] tags. These links are used for linking to the previous or next group of records when a set of records is returned in groups. They are useful when troubleshooting, or when creating manual links that function similarly to the [next] and [prev] tags. The result can also be used in a conditional statement. J8Displays the previous link created with the [prev] tag. [prev_url]N Accepts encoding parameters.P [prev_url] [prev_url] The [next_url] and [prev_url] tags are used to display the links created with the [next] [/next] and [prev] [/prev] tags. These links are used for linking to the previous or next group of records when a set of records is returned in groups. They are useful when troubleshooting, or when creating manual links that function similarly to the [next] and [prev] tags. The result can also be used in a conditional statement. Find Random RecordC ActionD -random The -random action finds a random record in the specified FileMaker Pro database. The sample syntax shows how to submit a random request with a button on an HTML form. When selected, a single random record will be retrieved from the specified database. The randomly selected record is displayed using the format file specified by the -response tag. The -random action can also be specified in an embedded URL which can be used in a hyperlink as follows: <a href="Lasso.acgi?-random&-databa se=YourDBName&-layout=YourLayoutName &-response=YouFileName.html"> Click here to see a random record</a> The name of the submit button must be -random and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-random"> The name parameter must specify the action, even if the action is specified elsewhere. In order to execute the -random action, the end user must have search permission for the database. If the user does not have search permission, a database security violation error is returned. J$Finds a random record in a database.L -randomO -FindAnyPE<input type="submit" name="-random" value="Retrieve a Random Record"> <input type="submit" name="-random" value="Retrieve a Random Record"> The -random action finds a random record in the specified FileMaker Pro database. The sample syntax shows how to submit a random request with a button on an HTML form. When selected, a single random record will be retrieved from the specified database. The randomly selected record is displayed using the format file specified by the -response tag. The -random action can also be specified in an embedded URL which can b e used in a hyperlink as follows: <a href="Lasso.acgi?-random&-database=YourDBName&-layout=YourLayoutName &-response=YouFileName.html"> Click here to see a random record</a> The name of the submit button must be -random and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-random"> The name parameter must specify the action, even if the action is specifieC d elsewhere. In order to execute the -random action, the end user must have search permission for the database. If the user does not have search permission, a database security violation error is returned. `A Record IDC CommandD -recid A specific record in a FileMaker Pro database can be identified by a unique number assigned to the record when it is created. The -recid tag can be used for specifying that the Lasso action be directed to a specific record. The -recid tag is required on format files that act upon a specific record such as with update, duplicate, delete actions. It is not needed otherwise. record ID value is not related to the unsorted order of the records in the database. As a record is ad ded to a database, the record ID is incremented and a unique number is assigned to that record. Once a record is deleted, that record ID is retired. If a record is exported and re-imported, the original ID number is lost and it is assigned a new record ID. If all records in a database are deleted or a clone of a database is created, the record ID numbering may begin again at record number one. This value cannot be retrieved using FileMaker Pro 3.x. However, in version 4.0, the record ID va lue can be retrieved using the calculation Status(CurrentRecordID) and can thus be used as a temporary unique identifier for that record. The -recid tag is typically used to specify that the action be directed at the record ID value that is retrieved with the [recid_value] tag. The [recid_value] is handy for keeping track of a specific record of a database. The value of the current record ID is substituted for [recid_value] when Lasso locates a record. A record ID can be targeted using the following syntax: &-recid=[recid_value] <input type="hidden name="-recid value="[recid_value]"> For example, when using an embedded URL, use the following syntax: <a href="action.lasso?search&-database=employees&-layout=main&-response=Detail.html&-recid=[recid_value]"> As another example, an inline can be directed to update the field (with the value of the client_username) for a specific record: [inline: update, database="employees", layout="main", name"=client_ username, recid=recid_value] User Name: [client_username] [/inline] In the above example, the specific record is updated after the file is processed, thus the previous action would have had to been some action that resulted in a single record being located. The -recid command tag can only be used on a post-Lasso format file, since Lasso must first identify the record and locate its identifier number. Specifies a database record.L -recidO -RecIDP9<input type="hidden" name="-recid" value="[recid_value]"> <input type="hidden" name="-recid" value="[recid_value]"> A specific record in a FileMaker Pro database can be identified by a unique number assigned to the record when it is created. The -recid tag can be used for specifying that the Lasso action be directed to a specific record. The -recid tag is required on format files that act upon a specific record such as with update, duplicate, delete actions. It is not needed otherwise. record ID value is not related to the unsor ted order of the records in the database. As a record is added to a database, the record ID is incremented and a unique number is assigned to that record. Once a record is deleted, that record ID is retired. If a record is exported and re-imported, the original ID number is lost and it is assigned a new record ID. If all records in a database are deleted or a clone of a database is created, the record ID numbering may begin again at record number one. This value cannot be retrieved using F ileMaker Pro 3.x. However, in version 4.0, the record ID value can be retrieved using the calculation Status(CurrentRecordID) and can thus be used as a temporary unique identifier for that record. The -recid tag is typically used to specify that the action be directed at the record ID value that is retrieved with the [recid_value] tag. The [recid_value] is handy for keeping track of a specific record of a database. The value of the current record ID is substituted for [recid_value] whe n Lasso locates a record. A record ID can be targeted using the following syntax: &-recid=[recid_value] <input type="hidden name="-recid value="[recid_value]"> For example, when using an embedded URL, use the following syntax: <a href="action.lasso?search&-database=employees&-layout=main&-response=Detail.html&-recid=[recid_value]"> As another example, an inline can be directed to update the field (with the value of the client_username) for a specific record: [inline: update, database="employees", layout="main", name"=client_username, recid=recid_value] User Name: [client_username] [/inline] In the above example, the specific record is updated after the file is processed, thus the previous action would have had to been some action that resulted in a single record being located. The -recid command tag can only be used on a post-Lasso format file, since Lasso must first identify the record and locate its identifier number. Record ID ValueC SubstitutionD [recid_value]I The value of the current record ID is substituted for [recid_value] when Lasso locates a record. See Record ID for more details. No spaces, parameters, or other text is valid within this tag.J+Inserts the value of the current record ID.L [recid_value]O [FMP-CurrentRecID]P9<input type="hidden" name="-recid" value="[recid_value]"> <input type="hidden" name="-recid" value="[recid_value]"> The value of the current record ID is substituted for [recid_value] when Lasso locates a record. See Record ID for more details. No spaces, parameters, or other text is valid within this tag. Record DisplayC ContainerD [record]E [/record] Everything between the [record] [/record] container tags will be repeated for every record returned from a database after a Lasso action. This includes any HTML formatting or elements such as lines, tables, or rows of a table. The [record] [/record] tags are optional if only one record is being displayed (for example, an Add Reply"). If the [record] tags are omitted and there is more than one record in the result set, then only the first record will be displayed. If the [record] tag is u sed, the ending [/record] tag must also be used to indicate the end of the record. The [field: ] tag can be placed outside of the [record] [/record] container to display the field s value for the first record in the found set. This is handy for summary or global fields, or if all the records in the found set have the same text value and you want to display title or header information. Other Lasso tags can also be placed outside of the [record] [/record] container, for example [server_ date] to display the current date; or [lasso-action] to display the previous Lasso action. In addition, any other container tags must be completely contained with the [record] [/record] container. For example, a conditional statement would need to end the [if] tag within the [record] [/record] container, as follows: [record] [if: (value) operator (value)] HTML if condition is true [else] HTML if condition is false [/if] [/record] Any field value that appeared within the condi tional statement would be from a specific record in the set of found records. Note that some HTML authoring programs may automatically delete the [record] and [/record] tags within tables. The solution is to put the tags within their own table cells, as follows: <table> <th>[record]</th> <tr><td> Here is the value of the field fieldname1 for this record: [field:fieldname1] The record identifier is: [recid_value] </td></tr> <tr><td> [/record] </td></tr> </table> Note that in the abovE]e the [recid_value] will return a number that represents the record ID for a specific record. JCRepeats display elements for every record returned from a database.L [record] ... [/record]N Within container: any valueO [FMP-Record] [/FMP-Record]P [record] [/record] [record] [/record] Everything between the [record] [/record] container tags will be repeated for every record returned from a database after a Lasso action. This includes any HTML formatting or elements such as lines, tables, or rows of a table. The [record] [/record] tags are optional if only one record is being displayed (for example, an Add Reply"). If the [record] tags are omitted and there is more than one record in the result set, then only the first record will be displayed. If the [record] tag is used, the ending [/record] tag must also be used to indicate the end of the record. The [field: ] tag can be placed outside of the [record] [/record] container to display the field s value for the first record in the found set. This is handy for summary or global fields, or if all the records in the found set have the same text value and you want to display title or header information. Other Lasso tags can also be placed outside of the [record] [/record] container, for example [server_date] to display the current date; or [lasso-action] to display the previous Lasso action. In addition, any other container tags must be completely contained with the [record] [/record] container. For example, a conditional statement would need to end the [if] tag within the [record] [/record] container, as follows: [record] [if: (value) operator (value)] HTML if condition is true [else] HTML if condition is false [/if] [/record] Any field value that appe ared within the conditional statement would be from a specific record in the set of found records. Note that some HTML authoring programs may automatically delete the [record] and [/record] tags within tables. The solution is to put the tags within their own table cells, as follows: <table> <th>[record]</th> <tr><td> Here is the value of the field fieldname1 for this record: [field:fieldname1] The record identifier is: [recid_value] </td></tr> <tr><td> [/record] </td></tr> </table> ErNote that in the above the [recid_value] will return a number that represents the record ID for a specific record. ReferrerC ContainerD [referrer]E [/referrer] Lasso will insert a link that represents the URL of the referring page using the [referrer] [/referrer]tag. The referrer is passed to Lasso from the browser, and is the URL of the page the user visited just prior to the currently viewed page that contains the [referrer] tag. The referrer can serve as a link on a format file, but only when it is available. The [referrer] tag can be used on any format file; however, your specific site will need to be evaluated to determine if it is ap propriate. The URL the server passes as the referrer will be inserted as the anchor. The text between the tags will be the link text. Here is the syntax of the tag as it appears in your format file: [referrer]Insert Link Text Here[/referrer] When processed, Lasso will automatically substitute a link back in the format: <a href="referringpage.html">Insert Link Text Here</a> For example, here is how the substituted link would appear for one specific site: <a href="http://www.bigser ver.com/project/add.html">Go Back</a> Keep in mind that the referrer URL may not be available to use as a back button. Since the referrer uses the URL of the previous page, it cannot be used to return to pages created by a action, that is, a submitted form. For example, in an add reply hitlist page, the link will return back to a blank version of the form (depending on how the add.html or search.html were originally called up). However, it would work if the previous page was : brought up using an URL with Lasso commands embedded in the URL, or if the previous page was a standard HTML file. To display the value of the referrer, the [referrer_url] tag can be used to substitute the referrer URL into the output HTML document. This can be useful for better understanding the referrer tag. J=Inserts a link that represents the URL of the referring page.L [referrer] ... [/referrer]N3Within container: text to appear on "Referrer" linkP [referrer]Go Back[/referrer] [referrer]Go Back[/referrer] Lasso will insert a link that represents the URL of the referring page using the [referrer] [/referrer]tag. The referrer is passed to Lasso from the browser, and is the URL of the page the user visited just prior to the currently viewed page that contains the [referrer] tag. The referrer can serve as a link on a format file, but only when it is available. The [referrer] tag can be used on any format file; however, your specific site will need to be eval uated to determine if it is appropriate. The URL the server passes as the referrer will be inserted as the anchor. The text between the tags will be the link text. Here is the syntax of the tag as it appears in your format file: [referrer]Insert Link Text Here[/referrer] When processed, Lasso will automatically substitute a link back in the format: <a href="referringpage.html">Insert Link Text Here</a> For example, here is how the substituted link would appear for one specific site <a href="http://www.bigserver.com/project/add.html">Go Back</a> Keep in mind that the referrer URL may not be available to use as a back button. Since the referrer uses the URL of the previous page, it cannot be used to return to pages created by a action, that is, a submitted form. For example, in an add reply hitlist page, the link will return back to a blank version of the form (depending on how the add.html or search.html were originally called up). However, it would X work if the previous page was brought up using an URL with Lasso commands embedded in the URL, or if the previous page was a standard HTML file. To display the value of the referrer, the [referrer_url] tag can be used to substitute the referrer URL into the output HTML document. This can be useful for better understanding the referrer tag. Display Referrer URLC SubstitutionD [referrer_url] !The [referrer_url] tag is used to display the referer link that is created with the [referrer] [/referrer] container tags. Instead of actually creating the link, it simply displays what the link is. It is useful when troubleshooting the referer link or for use in a conditional statement. J:Displays the referer link created with the [referer] tag. L [referrer_url]N Accepts encoding parameters.P [referrer_url] 1[referrer_url] The [referrer_url] tag is used to display the referer link that is created with the [referrer] [/referrer] container tags. Instead of actually creating the link, it simply displays what the link is. It is useful when troubleshooting the referer link or for use in a conditional statement. Display Repeat ValueC Sub-ContainerD [repeat_value] Values can be added to FileMaker Pro repeating fields, and then updated or displayed. The [repeat_value] tag will be substituted for the current values for the repeating field. This substitution tag is only valid within the [repeating: [/repeating] container. When displaying a repeating field, the number of repeats defined for that field on the specified layout will be returned with any entered values substituted. That is, all repeat values are returned when displayed. On an update orm, the number of repeats defined for that field (on the referenced FileMaker Pro layout) will be displayed, with any entered values substituted. When updating a repeating field, values will be inserted into the corresponding repeat. If you want fewer repeats to appear, format the repeating field to display fewer repeats on the referenced FileMaker Pro layout. Or, use the [loop_count] tag to limit the number of repeats displayed for a repeating field. For example, the following can be us ed to display the first five repeats only: [repeating:"YourFieldName"] [if: loop_count <= 5] <input type="text size=30 name="YourFieldName value="[repeat_value]"><br> [/if] [/repeating] Repeating fields can include value lists using the [value_list: ] and [option: ] tags inside of [repeating: ] tags. If there were repeating values, then the following HTML would create pop-up menus: [repeating: YourFieldName"] <select name="YourFieldName"> <option> <option selecte d>[repeat_value] [option: YourFieldName"] </select> [/repeating] Using the [value_list: ] tag the syntax would be similar to: [repeating: YourFieldName"] [value_list: YourFieldName"] <input type="radio name="YourFieldName value="[list_value] [checked]>[list_value] [/value_list]<br> [/repeating] Repeating fields within portals are not supported. The parameters smart, break, can be used to control how Lasso encodes special characters found in that field . For example, URL encoding can be applied to repeat values as follows: [repeating: YourFieldName"] [repeat_value,url] [/repeating] Important: Make sure that there are enough repeating fields on the specified FileMaker Pro layout as are included on your Lasso format file. There can be more repeating fields on the specified layout in FileMaker Pro than there are on the format file, but not the other way around. If you have more field repetitions specified in your HTML than are listed in the specified FileMaker Pro layout for the referenced field, you will receive a -1701 error from Lasso. The field must not only be defined to have a certain number of repetitions, but also formatted to display all of those repetitions on the specified FileMaker Pro layout. J3Inserts the current values for the repeating field.L [repeat_value]NZOnly valid within the [repeating:...] [/repeating] container. Accepts encoding parameters.O [FMP-RepeatingItem]Ps[repeating:YourFieldName] <input type="text" size=30 name="YourFieldName" value="[repeat_value]"><br> [/repeating] [repeating:YourFieldName] <input type="text" size=30 name="YourFieldName" value="[repeat_value]"><br> [/repeating] Values can be added to FileMaker Pro repeating fields, and then updated or displayed. The [repeat_value] tag will be substituted for the current values for the repeating field. This substitution tag is only valid within the [repeating: [/repeating] container. When displaying a repeating field, the number of repeats defined for that field on the specified layout will be r eturned with any entered values substituted. That is, all repeat values are returned when displayed. On an update form, the number of repeats defined for that field (on the referenced FileMaker Pro layout) will be displayed, with any entered values substituted. When updating a repeating field, values will be inserted into the corresponding repeat. If you want fewer repeats to appear, format the repeating field to display fewer repeats on the referenced FileMaker Pro layout. Or, use the [loop_count] tag to limit the number of repeats displayed for a repeating field. For example, the following can be used to display the first five repeats only: [repeating:"YourFieldName"] [if: loop_count <= 5] <input type="text size=30 name="YourFieldName value="[repeat_value]"><br> [/if] [/repeating] Repeating fields can include value lists using the [value_list: ] and [option: ] tags inside of [repeating: ] tags. If there were repeating values, then the following HTML woul d create pop-up menus: [repeating: YourFieldName"] <select name="YourFieldName"> <option> <option selected>[repeat_value] [option: YourFieldName"] </select> [/repeating] Using the [value_list: ] tag the syntax would be similar to: [repeating: YourFieldName"] [value_list: YourFieldName"] <input type="radio name="YourFieldName value="[list_value] [checked]>[list_value] [/value_list]<br> [/repeating] Repeating fields within portals are not supported. The paramet smart, break, can be used to control how Lasso encodes special characters found in that field. For example, URL encoding can be applied to repeat values as follows: [repeating: YourFieldName"] [repeat_value,url] [/repeating] Important: Make sure that there are enough repeating fields on the specified FileMaker Pro layout as are included on your Lasso format file. There can be more repeating fields on the specified layout in FileMaker Pro than there are on the fo rmat file, but not the other way around. If you have more field repetitions specified in your HTML than are listed in the specified FileMaker Pro layout for the referenced field, you will receive a -1701 error from Lasso. The field must not only be defined to have a certain number of repetitions, but also formatted to display all of those repetitions on the specified FileMaker Pro layout. Repeating FieldsC ContainerD [repeating: ...]E [/repeating] The [repeating: [/repeating] tags are used with the [repeat_value] tag to display all repeating values for the specified field. The [repeat_value] tag represents one repeat of the repeatiing field. It is repeated as many times as the number of repeats defined for that field, and which appear on the layout specified. All repeats for a field are returned, whether a value is entered into the repeat or not. To limit the number of repeats returned, adjust the number defined on the specified layout. The HTML code for the break tag (<BR clear="all">) can be used to clear any break tags that are not used for a repeat_value (that is, the repeat is blank). Repeating values can be separated by a comman and the following conditional statement used to produce a comma before every selection except the first: [repeating:"YourFieldName"][if: loop_count != 1], [/if][repeat_value] [/repeating] The [loop_count] tag returns the number of the repeat for any looping or repeating containe r tag. The values substituted for [repeat_value] can be used with any other surrounding HTML. For example, if you want to use the repeating field info to populate the values in a pop-up menu on a detail page: <p><select name="YourFieldName size=1> [repeating: YourFieldName"] <option value="[repeat_value] selected>[repeat_value] [/repeating] </select> Of course, this will only work on a detail layout when you return a record that has something in the repeating field. It will only D3show values for that specific record in the pop-up. J?Displays all repeating values for the specified database field.L![repeating: ...] ... [/repeating]N;Name of the field. Within container: the [repeat_value] tagO%[FMP-Repeating: ...] [/FMP-Repeating]PF[repeating:"YourFieldName"] [repeat_value]<br clear=all> [/repeating] [repeating:"YourFieldName"] [repeat_value]<br clear=all> [/repeating] The [repeating: [/repeating] tags are used with the [repeat_value] tag to display all repeating values for the specified field. The [repeat_value] tag represents one repeat of the repeatiing field. It is repeated as many times as the number of repeats defined for that field, and which appear on the layout specified. All repeats for a field are returned, whether a value is entered into the repeat or not. To limit th e number of repeats returned, adjust the number defined on the specified layout. The HTML code for the break tag (<BR clear="all">) can be used to clear any break tags that are not used for a repeat_value (that is, the repeat is blank). Repeating values can be separated by a comman and the following conditional statement used to produce a comma before every selection except the first: [repeating:"YourFieldName"][if: loop_count != 1], [/if][repeat_value] [/repeating] The [loop_count] ta g returns the number of the repeat for any looping or repeating container tag. The values substituted for [repeat_value] can be used with any other surrounding HTML. For example, if you want to use the repeating field info to populate the values in a pop-up menu on a detail page: <p><select name="YourFieldName size=1> [repeating: YourFieldName"] <option value="[repeat_value] selected>[repeat_value] [/repeating] </select> Of course, this will only work on a detail layout when you D{return a record that has something in the repeating field. It will only show values for that specific record in the pop-up. RepetitionC Sub-ContainerD [repetition] Conditional statements can test for the number of repetitions of a [record], [repeating], or [portal] tag. Based on this, they can display any HTML element or Lasso-returned value in that pattern. The format used is as follows: [record] blah [if: repetition=="2"] blah blah [/if] [/record] The above will insert blah blah for every other record. If the test was repetition = 3, then blah blah would be printed for every third record, and so on. This works for repeatin g and portal repetitions also, with the precedence in this order: repeating, portal, record. The [repetition] tag is especially useful to end the rows of a table at a specified point. Using [repetition] and a conditional statement, it is possible to put records in rows of a table and to change the look of every other row e.g., tabular data can be displayed with every other row shaded. Or, as is shown in the sample syntax, a radio button selection list can be formatted so that each radio b utton selection is separated into its own cell, with the row ending after five checkboxes, and starting in a new row. The same can be done for a checkbox selection list as follows: <table><tr> [value_list:"provisions"] <td><input type="checkbox name="provisions value="[list_value]"[checked]> [list_value]</td> [if: repetition==5]</tr><tr> [/if] [/value_list]</tr></table> <input type="hidden name="provisions value="">Unselect All In the above, each checkbox will be separated into iDRts own cell, the row will end after five checkboxes, and start again in a new row. JVSpecifies the number of a repetition within a [record], [repeating], or [portal] tag.L [repetition]NAOnly valid within a a [record], a [repeating], or a [portal] tag.P <table><tr> [value_list:"YourFieldName"] <td><input type=radio name="YourFieldName" value="[list_value]" [checked]>[list_value]</td> [if: repetition==5]</tr><tr> [/if] [/value_list]</tr></table> <table><tr> [value_list:"YourFieldName"] <td><input type=radio name="YourFieldName" value="[list_value]" [checked]>[list_value]</td> [if: repetition==5]</tr><tr> [/if] [/value_list]</tr></table> Conditional statements can test for the number of repetitions of a [record], [repeating], or [portal] tag. Based on this, they can display any HTML element or Lasso-returned value in that pattern. The format used is as follows: [record] blah [if: repetition=="2"] blah blah [/if] /record] The above will insert blah blah for every other record. If the test was repetition = 3, then blah blah would be printed for every third record, and so on. This works for repeating and portal repetitions also, with the precedence in this order: repeating, portal, record. The [repetition] tag is especially useful to end the rows of a table at a specified point. Using [repetition] and a conditional statement, it is possible to put records in rows of a table and to chang e the look of every other row e.g., tabular data can be displayed with every other row shaded. Or, as is shown in the sample syntax, a radio button selection list can be formatted so that each radio button selection is separated into its own cell, with the row ending after five checkboxes, and starting in a new row. The same can be done for a checkbox selection list as follows: <table><tr> [value_list:"provisions"] <td><input type="checkbox name="provisions value="[list_value]"[check ed]> [list_value]</td> [if: repetition==5]</tr><tr> [/if] [/value_list]</tr></table> <input type="hidden name="provisions value="">Unselect All In the above, each checkbox will be separated into its own cell, the row will end after five checkboxes, and start again in a new row. Required Field MissingC CommandD -reqfieldmissing A required field is used to assist the completion of the form by requiring that the field be completed before the form is submitted. The -reqFieldMissing command tag specifies a custom error page to be delivered when a required field is missing. If no format file is specified, Lasso will deliver a default error page. This error occurs if a form is submitted without a value entered into a field defined as required in the referenced FileMaker Pro database (fields may be required via the DeB fine Fields validation option in FileMaker Pro). Alternatively, the error may result from a field which has no value entered, but a required tag appears before the field on the add or search format file. JOSpecifies a custom error page to be delivered when a required field is missing.L -reqfieldmissingO -Error (plus a workaround)PN<input type="hidden" name="-reqfieldmissing" value="Pathto/YourFileName.html"> <input type="hidden" name="-reqfieldmissing" value="Pathto/YourFileName.html"> A required field is used to assist the completion of the form by requiring that the field be completed before the form is submitted. The -reqFieldMissing command tag specifies a custom error page to be delivered when a required field is missing. If no format file is specified, Lasso will deliver a default error page. This error occurs if a form is submitted without a value entered into a field defined as requi in the referenced FileMaker Pro database (fields may be required via the Define Fields validation option in FileMaker Pro). Alternatively, the error may result from a field which has no value entered, but a required tag appears before the field on the add or search format file. Required FieldC CommandD -required The -required tag can be used to require that someone enter values into the field before a form is submitted. This would be used on a search form that has several fields that you want to require values to be entered into. The -required tag is placed before an input field on a form, and applies only to the field that follows. The -required command can also be used in combination with another operator. Different operators or required command tags can be specified for several different fi elds on the same form. Any form that was submitted without values entered into the required field would be rejected. In this case, Lasso displays a required field missing error. A customized error page can be used in place of the default message. The required field error page is specified with the -reqFieldMissing tag. The (optional) customized error is specified as: <input type="hidden name="-reqFieldMissing value="FileName.html"> See the -reqFieldMissing tag for more details. iJFRequires values to be entered into a field before a form is submitted.L -requiredO"(accomplished via FM Pro commands)P <input type="hidden" name="-required"> <input type="hidden" name="-operator" value="eq"> <input type="text" name="YourFieldName" size="30"> <input type="hidden" name="-required"> <input type="hidden" name="-operator" value="eq"> <input type="text" name="YourFieldName" size="30"> The -required tag can be used to require that someone enter values into the field before a form is submitted. This would be used on a search form that has several fields that you want to require values to be entered into. The -required tag is placed before an input field on a form, and applies only to the field that follows. The -required command can also be used in combination with another operator. Different operators or required command tags can be specified for several different fields on the same form. Any form that was submitted without values entered into the required field would be rejected. In this case, Lasso displays a required field missing error. A customized error page can be used in place of the default message. The required field error page is specified with the -reqFieldMissing tag. The (optional) customized eC rror is specified as: <input type="hidden name="-reqFieldMissing value="FileName.html"> See the -reqFieldMissing tag for more details. ResponseC CommandD -response The -response tag indicates the name of the format file to use for displaying the results of a Lasso action. The -response tag is required for all Lasso actions except -nothing, or when an action is specified within an inline. Some other notes on -response: The name of files and directories are not case-sensitive. All format files must be located within the Web serving folder. A format file on another server cannot be referenced. The path to a format file can refer to an alias o f the format file. An absolute path can be used if it specifies all directories that lead to the referenced file. A slash can be used at the start of the path to indicate that it begins at the root level of the Web serving folder. For post-Lasso format files, the response is specified as relative from the active URL. In other words, if a format file is located within the same directory as the current format file, the reference will simply be the name of the file. If located in a diff erent folder of format files, the path will need to reflect that. When a response is specified on a pre-Lasso format file, the location is relative from the action attribute of the HTML form tag. For example, if the action is at the root level using: <form action="\action.lasso method="post"> Then, the response should be specified from the root level. A database field may be specified for the response; in this case Lasso will process the contents of the field for the response format file. The advantage is that Lasso does not need to retrieve a format file from disk. For example, an embedded URL would appear as: <a href="\action.lasso?-database=dynamo&-layout=web&-response=field:fieldName If used within an HTML form, the response field can be specified by a hidden input as follows: <input type="hidden name="-response value="field:fieldName"> In this example, fieldname is the actual name of the field In this case it is not surrounded by quotes, since the quo tes would conflict with HTML tagging to indicate the value. Lasso should retrieve the response format from. All Lasso tags contained in the field data would be processed and replaced. HTML can be stored in the field to format any data that is returned for display. An extra option has been added to the security databases to turn this feature on. This method can also be used with any other response tag including: -duplicatereply, -addError, -deleteReply, -noResults, -reqFieldMissing, (and -emailformat. Note: -response is synonymous with either [filename] or [format], which were used in earlier versions of Lasso. However, -response is the preferred specification, and future versions of Lasso may not support [filename] or [format]. Lasso Lite supports only the use of [format]. JNSpecifies the format file to use for displaying the results of a Lasso action.L -responseO -FormatPG<input type="hidden" name="-response" value="Pathto/YourFileName.html"> <input type="hidden" name="-response" value="Pathto/YourFileName.html"> The -response tag indicates the name of the format file to use for displaying the results of a Lasso action. The -response tag is required for all Lasso actions except -nothing, or when an action is specified within an inline. Some other notes on -response: The name of files and directories are not case-sensitive. All format files must be located within the Web serving folder. A format file on another server ca nnot be referenced. The path to a format file can refer to an alias of the format file. An absolute path can be used if it specifies all directories that lead to the referenced file. A slash can be used at the start of the path to indicate that it begins at the root level of the Web serving folder. For post-Lasso format files, the response is specified as relative from the active URL. In other words, if a format file is located within the same directory as the current format file , the reference will simply be the name of the file. If located in a different folder of format files, the path will need to reflect that. When a response is specified on a pre-Lasso format file, the location is relative from the action attribute of the HTML form tag. For example, if the action is at the root level using: <form action="\action.lasso method="post"> Then, the response should be specified from the root level. A database field may be specified for the response; in this c ase Lasso will process the contents of the field for the response format file. The advantage is that Lasso does not need to retrieve a format file from disk. For example, an embedded URL would appear as: <a href="\action.lasso?-database=dynamo&-layout=web&-response=field:fieldName If used within an HTML form, the response field can be specified by a hidden input as follows: <input type="hidden name="-response value="field:fieldName"> In this example, fieldname is the actual nam e of the field In this case it is not surrounded by quotes, since the quotes would conflict with HTML tagging to indicate the value. Lasso should retrieve the response format from. All Lasso tags contained in the field data would be processed and replaced. HTML can be stored in the field to format any data that is returned for display. An extra option has been added to the security databases to turn this feature on. This method can also be used with any other response tag including: q -duplicatereply, -addError, -deleteReply, -noResults, -reqFieldMissing, and -emailformat. Note: -response is synonymous with either [filename] or [format], which were used in earlier versions of Lasso. However, -response is the preferred specification, and future versions of Lasso may not support [filename] or [format]. Lasso Lite supports only the use of [format]. Display Response File NameC SubstitutionD [response_file_path] The [response_file_path] tag can be used to retrieve the name and path to the current response file. It will display the file that was specified by the -response tag in the Lasso action used to call up the currently viewed page.JFRetrieves the name and path to the file specified by the -response tagL [response_file_path]N Accepts encoding parameters.O [FMP-CurrentFormat] P [response_file_path]Q [response_file_path] The [response_file_path] tag can be used to retrieve the name and path to the current response file. It will display the file that was specified by the -response tag in the Lasso action used to call up the currently viewed page. Execute FileMaker Pro ScriptC ActionD -scripts The -scripts action tag is used in conjunction with the -doscript tag, to create a button that will execute a script as a single action. The nothing tag can also be used with the -doscript tag to achieve the same result. The -scripts action can be used as the action on an HTML form, in a URL link, or by an inline. Note that there are six variations of the -doscript tag: doscript.post doscript.pre doscript.presort doscript.pre.back doscript.post.back doscript.presort.back -doscript s specified, it is assumed that this is the -doscript.post tag. When used on a form -scripts can be incorporated into a submit button, as shown in the sample syntax. In that example, the value for Run FileMaker Scripts can be any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-scripts"> The name parameter must specify the action, even if the action is specified elsewhere. The -doscript and -scripts tags can also be embedded in a URL. If using the Plug-in version, an example URL is as follows: <a href="action.lasso?-database=employees&-layout=main&-response=detail.html& -doscript=accumulate&-scripts">Run Script</a> A script can be activated by an inline action. For example: [inline: scripts, database=employees, layout=main, response=detail.html, doscript=accumulate] [/inline] The inline will be executed when Lasso processes the file this code is locatD ed on. JYUsed in conjunction with the -doscript tag to create a button that will execute a script.L -scriptsO -FindAllP <input type="hidden" name="-doscript.post" value="YourScriptName"> <input type="submit" name="-scripts" value="Run FileMaker Script"> <input type="hidden" name="-doscript.post" value="YourScriptName"> <input type="submit" name="-scripts" value="Run FileMaker Script"> The -scripts action tag is used in conjunction with the -doscript tag, to create a button that will execute a script as a single action. The nothing tag can also be used with the -doscript tag to achieve the same result. The -scripts action can be used as the action on an HTML form, in a URL link, or by an inline. Note that there are six variations of the - doscript tag: doscript.post doscript.pre doscript.presort doscript.pre.back doscript.post.back doscript.presort.back -doscript is specified, it is assumed that this is the -doscript.post tag. When used on a form -scripts can be incorporated into a submit button, as shown in the sample syntax. In that example, the value for Run FileMaker Scripts can be any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type=" Image src="searchgraphic.gif name="-scripts"> The name parameter must specify the action, even if the action is specified elsewhere. The -doscript and -scripts tags can also be embedded in a URL. If using the Plug-in version, an example URL is as follows: <a href="action.lasso?-database=employees&-layout=main&-response=detail.html& -doscript=accumulate&-scripts">Run Script</a> A script can be activated by an inline action. For example: [inline: scripts, database=employees, layout=mD ain, response=detail.html, doscript=accumulate] [/inline] The inline will be executed when Lasso processes the file this code is located on. SearchC ActionD -search The -search action completes a in the specified FileMaker Pro database. The sample syntax shows how to submit a search request with a button on an HTML form. Selecting the button will instruct Lasso to use the entered form data as the search parameters for finding records. If all fields on a search form are left blank then Lasso will report No records found. The name of the submit button must be -search and the value is any text you want to appear on the button. Images may als o be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-search"> The name parameter must specify the action, even if the action is specified elsewhere. The search action can be part of a URL link as follows: <a href="action.lasso?-search&-database=name&-layout=name&-response=name.html& -op=eq&fieldname=[field:fieldname,url]&fieldname2=[form_param:fieldname2,url]& -maxRecords=20&-sortfield=[field:fieldname,url]"> Search </a> Note that this URL approach can only be used on a post-Lasso form in which the previous format file provided data for the [field:fieldname] and fieldname2=[form_param:fieldname2,url] values. Otherwise the values could be literal, predetermined values. Be sure to encode any spaces in the URL with a plus sign and to use the parameter with any FileMaker Pro database fields so the returned data is encoded for use on a URL, i.e., [field:fieldname,url]. In the case when you have one field on a form, it is possible to have the Enter key submit the single-field form when the cursor is placed in that text input field. To do so you must add a second hidden action as follows: <input type="hidden name="-search"> This is good practice since if the second input is missing, Lasso returns a -50, Object not found error after someone hits the Enter key. With this in place, if the user clicks the submit button the search parameter will get sent twice, but Lasso w ill ignore the second (blank) search action. As another option, you could specify the action by combining it with the form action and other elements of the form. Using this method, the form action would begin as: <form action="action.lasso?-search&-database=Employees&-layout=summary& " method="post"> rest of the HTML form </form> With this syntax, the action will not be lost if the return key is selected. Note that, in any case, when a form contains several fields, pressing F{the Enter or Return keys will not cause the form to be submitted (nothing will occur). This functionality is not possible. J;Completes a "find" in the specified FileMaker Pro database.L -searchO -FindP9<input type="submit" name="-search" value="Start Search"> <input type="submit" name="-search" value="Start Search"> The -search action completes a in the specified FileMaker Pro database. The sample syntax shows how to submit a search request with a button on an HTML form. Selecting the button will instruct Lasso to use the entered form data as the search parameters for finding records. If all fields on a search form are left blank then Lasso will report No records found. The name of the submit button must be -search and the value i s any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-search"> The name parameter must specify the action, even if the action is specified elsewhere. The search action can be part of a URL link as follows: <a href="action.lasso?-search&-database=name&-layout=name&-response=name.html& -op=eq&fieldname=[field:fieldname,url]&fieldname2=[form_param:fieldname2,url]& xRecords=20&-sortfield=[field:fieldname,url]"> Search </a> Note that this URL approach can only be used on a post-Lasso form in which the previous format file provided data for the [field:fieldname] and fieldname2=[form_param:fieldname2,url] values. Otherwise the values could be literal, predetermined values. Be sure to encode any spaces in the URL with a plus sign and to use the parameter with any FileMaker Pro database fields so the returned data is encoded for use on a URL, i.e., [field:fieldname,url]. In the case when you have one field on a form, it is possible to have the Enter key submit the single-field form when the cursor is placed in that text input field. To do so you must add a second hidden action as follows: <input type="hidden name="-search"> This is good practice since if the second input is missing, Lasso returns a -50, Object not found error after someone hits the Enter key. With this in place, if the user clicks the submit b utton the search parameter will get sent twice, but Lasso will ignore the second (blank) search action. As another option, you could specify the action by combining it with the form action and other elements of the form. Using this method, the form action would begin as: <form action="action.lasso?-search&-database=Employees&-layout=summary& " method="post"> rest of the HTML form </form> With this syntax, the action will not be lost if the return key is selected. Note that, F in any case, when a form contains several fields, pressing the Enter or Return keys will not cause the form to be submitted (nothing will occur). This functionality is not possible. Display Search ArgumentsC ContainerD [search_args]E [/search_args] The tags used between the [search_args] [/search_args] container can display the parameters used on the previous search (typically on the hitlist return page). This includes the sub-container tags: [search_field], [search_op], and [search_value]. These tags are valid only within the search_args container, and one or all can be used. [search_field] Will display the name of the field the search was made on [search_value] Will display the value entered for the search for a particula r [search_field]. [search_op] Will display the operators applied to the [search_field]. [search_op] accepts the optional parameters short and long, as in [search_op,short]. The default is which inserts the field operator in its long form: equals, begins with, greater than, etc. Short uses the Lasso abbreviations etc. Specify short if using [search_op] to create a URL. Everything between the [search_args] [/search_args] container will be repeated for every field used for the search: [search_args] Field Searched: [search_field]<br> Operator: [search_op] <br> Value Entered: [search_value] <br><HR> [/search_args] The previous search arguments can be included within an embedded URL as follows: [search_args]&-op=[search_op,short]&[search_field,url]=[search_value,url][/search_args]" Fields that are not used for the search, but are on the search form, will not be included. For example, with the above syntax, the search argume nts may appear as: Field Searched: First Name Operator: begins with Value Entered: joe Field Searched: Last Name Operator: begins with Value Entered: smith Field Searched: Shift Operator: begins with Value Entered: 2 These tags accept the optional parameter that prevents Lasso from applying HTML character encoding. The parameter can also be used to specify URL encoding, as follows: Field/ Operator/ Value:<br> [search_args]"[search_field,url] [search_op,url] [search_val ue,url]<p> [/search_args] If the opbegin and opend tags were used on the search page, then this will also be reported in the search arguments, as follows: Field Searched: opbegin Operator: Value Entered: not To not have this occur, add the no_ops parameter as follows: [search_args,no_ops] [/search_args] The field level logical operators will not be displayed with the search args. J4Displays the parameters used on the previous search.L [search_args] ... [/search_args]NQno_ops, Within container: [search_field], [search_op] , and [search_value] tagsO$[FMP-CurrentFind] [/FMP-CurrentFind]P][search_args] [search_field] [search_op] [search_value] <br clear="all"> [/search_args] [search_args] [search_field] [search_op] [search_value] <br clear="all"> [/search_args] The tags used between the [search_args] [/search_args] container can display the parameters used on the previous search (typically on the hitlist return page). This includes the sub-container tags: [search_field], [search_op], and [search_value]. These tags are valid only within the search_args container, and one or all can be used. [search_field] Will display the name of the field the sear ch was made on [search_value] Will display the value entered for the search for a particular [search_field]. [search_op] Will display the operators applied to the [search_field]. [search_op] accepts the optional parameters short and long, as in [search_op,short]. The default is which inserts the field operator in its long form: equals, begins with, greater than, etc. Short uses the Lasso abbreviations etc. Specify short if using [search_op] to create a URL. Everything between the [search_args] [/search_args] container will be repeated for every field used for the search: [search_args] Field Searched: [search_field]<br> Operator: [search_op] <br> Value Entered: [search_value] <br><HR> [/search_args] The previous search arguments can be included within an embedded URL as follows: [search_args]&-op=[search_op,short]&[search_field,url]=[search_value,url][/search_args]" Fields that are not used for the search, but are on the search form, will not be included. For example, with the above syntax, the search arguments may appear as: Field Searched: First Name Operator: begins with Value Entered: joe Field Searched: Last Name Operator: begins with Value Entered: smith Field Searched: Shift Operator: begins with Value Entered: 2 These tags accept the optional parameter that prevents Lasso from applying HTML character encoding. The parameter can also be used to specify URL encoding, as foll Field/ Operator/ Value:<br> [search_args]"[search_field,url] [search_op,url] [search_value,url]<p> [/search_args] If the opbegin and opend tags were used on the search page, then this will also be reported in the search arguments, as follows: Field Searched: opbegin Operator: Value Entered: not To not have this occur, add the no_ops parameter as follows: [search_args,no_ops] [/search_args] The field level logical operators will not be displayed with the search args. Display Field SearchedC Sub-ContainerD [search_field]I The [search_field] tag will display the name of the field used for a -search action. It is only valid within the [search_args] [/search_args] container; refer to that tag for more information. Each field with a value associated with it will be returned. JEDisplays the name of the field used for a -search or -findall action.L [search_field]N[Only valid within the [search_args] [/search_args] container. Accepts encoding parameters. [FMP-FindFieldItem]P [search_field] [search_field] The [search_field] tag will display the name of the field used for a -search action. It is only valid within the [search_args] [/search_args] container; refer to that tag for more information. Each field with a value associated with it will be returned. Display Search OperatorC Sub-ContainerD [search_op] The [search_op] tag will display the operators applied to a field as part of a -search action. It is only valid within the [search_args] [/search_args] container; refer to that tag for more information. The optional parameters short and can be used in the format [search_op,short]. The default is long, which inserts the field operator in its long form: equal, begins with, greater than, etc. Short uses the Lasso abbreviations etc. Specify short if usinB g [search_op] to create a URL. JRDisplays the operators applied to a field as part of a -search or -findall action. [search_op]N[Only valid within the [search_args] [/search_args] container. Accepts encoding parameters.O [FMP-FindOpItem]P [search_op] [search_op] The [search_op] tag will display the operators applied to a field as part of a -search action. It is only valid within the [search_args] [/search_args] container; refer to that tag for more information. The optional parameters short and can be used in the format [search_op,short]. The default is long, which inserts the field operator in its long form: equal, begins with, greater than, etc. Short uses the Lasso abbreviations etc. Specify sB+hort if using [search_op] to create a URL. Display Search ValueC Sub-ContainerD [search_value] The [search_value] tag will display the value entered for a specific field on a -search action. It is only valid within the [search_args] [/search_args] container; refer to that tag for more information. Each value entered as part of the search will be returned. JPDisplays the value entered for a specific field on a -search or -findall action.L [search_value] NZOnly valid within the [search_args] [/search_args] container. Accepts encoding parameters.O [FMP-FindValueItem]P [search_value] [search_value] The [search_value] tag will display the value entered for a specific field on a -search action. It is only valid within the [search_args] [/search_args] container; refer to that tag for more information. Each value entered as part of the search will be returned. SelectedC Sub-ContainerD [selected] The [selected] tag instructs Lasso to place the selected parameter into the HTML element for the items selected in the database. It can only be used with the [value_list: [/value_list] container. It is most relevant when used with pop-up selection lists. The [selected] tag simply returns the text selected if an item on a value list has been selected. The item must be part of the value list associated with the field specified by the [value_list] tag. It is useful when used within `a conditional statement to determine if a value list item is currently selected for a specific record in the database, since selected will appear if that item is a value in that field. Within conditional statements, the [checked] and [selected] tags are interchangeable and produce the same result. For more details, refer to the [value_list: ] tag. J]Places the "selected" parameter into the HTML element for the items selected in the database.L [selected] rN>Only valid within the [value_list:...] [/value_list] containerO [FMP-ValueListChecked]P <select name="YourFieldName"> [value_list:"YourFieldName"] <option value="[list_value]" [selected]>[list_value] [/value_list] </select> <select name="YourFieldName"> [value_list:"YourFieldName"] <option value="[list_value]" [selected]>[list_value] [/value_list] </select> The [selected] tag instructs Lasso to place the selected parameter into the HTML element for the items selected in the database. It can only be used with the [value_list: [/value_list] container. It is most relevant when used with pop-up selection lists. The [selected] tag simply returns the text selected if an item on a value list has been selected. The item must be part of the value list associated with the field specified by the [value_list] tag. It is useful when used within a conditional statement to determine if a value list item is currently selected for a specific record in the database, since selected will appear if that item is a value in that field. Within conditional statements, the [checked] and [selected] tags are interchangeable and produce the same result. For more details, refer to the [value_list: ] tag. Display Current DateC SubstitutionD [server_date] The [server_date] tag inserts the current date into the output HTML. The date format is determined by three optional parameters: [server_date,short] will display the date as: 1/1/97. [server_date,abbrev] will display the date as: Wed, Jan 1, 1997. [server_date,long] will display the date as: Wednesday, January 1, 1997. The default is short. This tag was [date] with versions of Lasso previous to Lasso 2.0. sJ.Inserts the current date into the output HTML.L [server_date]N Accepts encoding parameters.O [FMP-CurrentDate]P [server_date] [server_date] The [server_date] tag inserts the current date into the output HTML. The date format is determined by three optional parameters: [server_date,short] will display the date as: 1/1/97. [server_date,abbrev] will display the date as: Wed, Jan 1, 1997. [server_date,long] will display the date as: Wednesday, January 1, 1997. The default is short. This tag was [date] with versions of Lasso previous to Lasso 2.0. Display Current DayC SubstitutionD [server_day] The [server_day] tag inserts the day of the week into the output HTML. The date format is determined by two optional parameters: [server_day, short] will display as a three-letter abbreviation in all capital letters (MON, TUE, etc.). [server_day, long] will display in mixed-case letters (Monday, Tuesday, etc.). The default is short. This tag was [day] with versions of Lasso previous to Lasso 2.0. J1Inserts the day of the week into the output HTML.L [server_day]N Accepts encoding parameters.O [FMP-CurrentDay]P [server_day] [server_day] The [server_day] tag inserts the day of the week into the output HTML. The date format is determined by two optional parameters: [server_day, short] will display as a three-letter abbreviation in all capital letters (MON, TUE, etc.). [server_day, long] will display in mixed-case letters (Monday, Tuesday, etc.). The default is short. This tag was [day] with versions of Lasso previous to Lasso 2.0. Display Server TimeC SubstitutionD [server_time] dThe [server_time] tag inserts the current time into the output HTML. The time format is determined by two optional parameters: [server_time,short] will display the hour and minutes, e.g., hh:mm [server_time,long] will also display the seconds, e.g., hh:mm:ss The default is short." This tag was [time] with versions of Lasso previous to Lasso 2.0. J.Inserts the current time into the output HTML.L [server_time]N Accepts encoding parameters.O [FMP-CurrentTime]P [server_time] s[server_time] The [server_time] tag inserts the current time into the output HTML. The time format is determined by two optional parameters: [server_time,short] will display the hour and minutes, e.g., hh:mm [server_time,long] will also display the seconds, e.g., hh:mm:ss The default is short." This tag was [time] with versions of Lasso previous to Lasso 2.0. Set a Cookie ValueC SubstitutionD [set_cookie: ...] Cookies are pieces of information saved in the browser settings of the guest computer. Lasso has the ability to set HTTP cookie values using the [set_cookie: ] command in a Lasso format file, and to retrieve that cookie using [cookie: cookie_name]. For example, a cookie may be set as: [set_cookie: Login"="arrival",expires=20000] In this example, Login is the name of the cookie, and arrival is the value it is set to. The action of setting a cookie saves a piece of data relevant to the user, and enables this data to be associated with a value so it can be recalled during the visit to the site, and/or on subsequent visits. cookie_name and cookie_value specify the name and value for the cookie. The other attributes expires, path, domain, and secure are optional and may appear in any order. Values for each can be literal text, a Lasso substitution tag, or a field value. To specify a field value, use the Lasso field tag, which is followed by a colon a nd the name of the field in quotes. For example: [set_cookie: cookie_name"=field:"userid"] Quotes around the name of the field are optional, but help identify to Lasso that it is a literal value and not a Lasso tag. The name of the cookie is a literal name you create; in the case of the sample syntax it is shown as cookie_name. As a parameter, cookie_name must be paired with a value, in the sample syntax it is shown as cookie_value. Both must be less than 1024 characters. The ookie_name parameter must appear first in the parameter list immediately following set_cookie: (a space does not matter). Since Lasso performs URL-style encoding and decoding of cookie names. Thus semi-colon, comma, or space characters can be used, even though Netscape prohibits their use in cookie names. Record IDs can be used by specifying recid_value (without the quotes) for the cookie value. s a description of each of the other parameters: expires The number of minutes in the future that the cookie will expire. path Sets the path attribute for the cookie. If not specified, the path defaults to the path of the active URL (at the time when the format file with the set_cookie tag is processed). domain Sets the domain attribute for the cookie. secure If specified, the cookie will be transmitted only over secure communications channels using the HTTPS (HTTP over SSL) protocol. Values associated with the other parameters should be enclosed iF n quotes. The total number of characters between the opening and closing square brackets of the [set_cookie: ] tag must be less than 2048. Sets an HTTP cookie.L [set_cookie: ...]N2expires, path, domain,secure, and any named cookieO [FMP-SetCookie: ...]Pl[set_cookie: "cookie_name"="cookie_value", expires="minutes", path="path_name", domain="domain_name",secure] [set_cookie: "cookie_name"="cookie_value", expires="minutes", path="path_name", domain="domain_name",secure] Cookies are pieces of information saved in the browser settings of the guest computer. Lasso has the ability to set HTTP cookie values using the [set_cookie: ] command in a Lasso format file, and to retrieve that cookie using [cookie: cookie_name]. For example, a cookie may be set as: [set_cookie: Login"="arrival",expires=20000] In this example, Login is the name of the cook ie, and arrival is the value it is set to. The action of setting a cookie saves a piece of data relevant to the user, and enables this data to be associated with a value so it can be recalled during the visit to the site, and/or on subsequent visits. cookie_name and cookie_value specify the name and value for the cookie. The other attributes expires, path, domain, and secure are optional and may appear in any order. Values for each can be literal text, a Lasso substitut ion tag, or a field value. To specify a field value, use the Lasso field tag, which is followed by a colon and the name of the field in quotes. For example: [set_cookie: cookie_name"=field:"userid"] Quotes around the name of the field are optional, but help identify to Lasso that it is a literal value and not a Lasso tag. The name of the cookie is a literal name you create; in the case of the sample syntax it is shown as cookie_name. As a parameter, cookie_name must be paired wi th a value, in the sample syntax it is shown as cookie_value. Both must be less than 1024 characters. The cookie_name parameter must appear first in the parameter list immediately following set_cookie: (a space does not matter). Since Lasso performs URL-style encoding and decoding of cookie names. Thus semi-colon, comma, or space characters can be used, even though Netscape prohibits their use in cookie names. Record IDs can be used by specifying recid_value (without the quotes) fo r the cookie value. s a description of each of the other parameters: expires The number of minutes in the future that the cookie will expire. path Sets the path attribute for the cookie. If not specified, the path defaults to the path of the active URL (at the time when the format file with the set_cookie tag is processed). domain Sets the domain attribute for the cookie. secure If specified, the cookie will be transmitted only over secure communications channeF ls using the HTTPS (HTTP over SSL) protocol. Values associated with the other parameters should be enclosed in quotes. The total number of characters between the opening and closing square brackets of the [set_cookie: ] tag must be less than 2048. Set a VariableC SubstitutionD [set_var: ...] The [set_var: ] tag is used to set the value of a named variable. Any number of variables can be created with one [set_var: ] tag by pairing the name of the variable with the value it is being set to. As opposed to a token, the value of the variable can be used only within the same page that it is set on (a token value is only available on the following reply page). There are three instances in which variables can be of great usefulness: 1. To retrieve a value that is a result of an i nline action. For example: [inline: search, database="Primary", layout="main", op="eq", Name"=field:"userid"] [set_var: field:"Name"] [/inline] The value that resulted from the inline action can thus be used outside of the inline container. 2. To evaluate a conditional statement once and then use that result repeatedly throughout the processed file. For example: [if: var: >> field: Category"] [set_var: Open"="True"] [else] [set_var: Open"="False"] [/if] The variable can \then be used elsewhere without having to check the condition again. 3. To set a variable to the value of a sub-container tag. For example: [sort_args][if: loop_count == 1] [set_var: sortedfield"=sort_field] [set_var: sortedby"=sort_order] [/if] [/sort_args] The value of the sub-container tag can thus be used outside of the container tag. J#Sets the value of a named variable.L [set_var: ...]N any named variableP6[set_var: "var1"="SomeValue", "var2"="SomeOtherValue"] [set_var: "var1"="SomeValue", "var2"="SomeOtherValue"] The [set_var: ] tag is used to set the value of a named variable. Any number of variables can be created with one [set_var: ] tag by pairing the name of the variable with the value it is being set to. As opposed to a token, the value of the variable can be used only within the same page that it is set on (a token value is only available on the following reply page). There are three instances in which variables can be of great usef ulness: 1. To retrieve a value that is a result of an inline action. For example: [inline: search, database="Primary", layout="main", op="eq", Name"=field:"userid"] [set_var: field:"Name"] [/inline] The value that resulted from the inline action can thus be used outside of the inline container. 2. To evaluate a conditional statement once and then use that result repeatedly throughout the processed file. For example: [if: var: >> field: Category"] [set_var: Open"="True"] [set_var: Open"="False"] [/if] The variable can then be used elsewhere without having to check the condition again. 3. To set a variable to the value of a sub-container tag. For example: [sort_args][if: loop_count == 1] [set_var: sortedfield"=sort_field] [set_var: sortedby"=sort_order] [/if] [/sort_args] The value of the sub-container tag can thus be used outside of the container tag. Show RecordC ActionD -show kThe -show action tag displays and search forms auto-populated with values from a targeted FileMaker Pro database. Lasso retrieves information that applies to all records in a database, for example, values used for selection lists. The -show action does not retrieve field data from specific records (or a found set of records) in a FileMaker Pro database. JdDisplays "add" and "search" forms auto-populated with values from a targeted FileMaker Pro database.L -showO -ViewP <a href="action.lasso?-database=YourDatabaseName&-layout=YourLayoutName&-response=Pathto/YourFileName.html&-show">display form</a> <a href="action.lasso?-database=YourDatabaseName&-layout=YourLayoutName&-response=Pathto/YourFileName.html&-show">display form</a> The -show action tag displays and search forms auto-populated with values from a targeted FileMaker Pro database. Lasso retrieves information that applies to all records in a database, for example, values used for selection lists. The -show action does not retrieve field data from specific records (or a found set of records) in a FileMaker Pro databaseB Skip Returned RecordsC CommandD -skiprecords The -skiprecords tag can be used to skip a specified number of records when displaying the returned found set of records. This command is optional. The [next] and [prev] tags should be included on the hitlist format file to create links to the previous or next group of records. For example, in the following syntax the first 10 records would be skipped: <input type="hidden name="-skiprecords value="10"> The value of this tag can be returned to the reply page using the [skiprecords_vaB tag. JVSkips a specified number of records when displaying the returned found set of records.L -skiprecordsO -SkipP`<select name="-skiprecords" size=1> <option>0 <option>5 <option>10 <option>20 </select> <select name="-skiprecords" size=1> <option>0 <option>5 <option>10 <option>20 </select> The -skiprecords tag can be used to skip a specified number of records when displaying the returned found set of records. This command is optional. The [next] and [prev] tags should be included on the hitlist format file to create links to the previous or next group of records. For example, in the following syntax the first 10 records would be skipped: <input type="hidden name="-skiprecordBls value="10"> The value of this tag can be returned to the reply page using the [skiprecords_value] tag. Display Skip Records ValueC SubstitutionD [skiprecords_value] lThe [skiprecords_value] tag is used to display the parameters used on the previous search (typically on the hitlist return page). The [skiprecords_value] will be substituted with a number representing the total records to be skipped in the returned set of found records. The skiprecords value is specified with the original search form or URL (the default is 0). JUSubstitutes the number of records to be skipped in the returned set of found records.L [skiprecords_value]N Accepts encoding parameters.O [FMP-CurrentSkip]P [skiprecords_value] [skiprecords_value] The [skiprecords_value] tag is used to display the parameters used on the previous search (typically on the hitlist return page). The [skiprecords_value] will be substituted with a number representing the total records to be skipped in the returned set of found records. The skiprecords value is specified with the original search form or URL (the default is 0). Display Sort ParametersC Container [sort_args]E [/sort_args] The tags used between the [sort_args] [/sort_args] container will display the parameters used on the previous search (typically on the hitlist return page). The [sort_field] and [sort_order] tags will display values for each instance of the sort parameters used on the previous search. [sort_field] Will display the name of the field used to sort the current found set of records. It is specified as part of a -search or -findall action by the [sort_field] tag. [sort_order] Will displ ay the order used for the sort on the current found set of records. It is specified as part of a -search or -findall action by the [sortorder] tag. The sort criteria can be included within an embedded URL as follows: [sort_args]&-sortfield=[sort_field,url]&-sortorder=[sort_order,url][/sort_args]& This is useful when constructing a link that redoes a previous search, when the search used multiple fields to sort the returned set of records. These tags are only valid within the [sort_ args] container, and one or both can be used. All HTML appearing between [sort_args] and [/sort_args] is repeated for every field included in the search: [sort_args] Field Used on Sort: [sort_field] Order: [sort_order] [/sort_args] These tags accept the optional parameter that prevents Lasso from applying HTML character encoding. The parameter can also be used to specify URL encoding. If omitted, HTML encoding is performed by default. {J4Displays the parameters used on the previous search.L [sort_args] ... [/sort_args]NEWithin container: the [sort_field] or [sort_order] substitution tagsO$[FMP-CurrentSort] [/FMP-CurrentSort]P5[sort_args][sort_field] [sort_order]<br> [/sort_args] [sort_args][sort_field] [sort_order]<br> [/sort_args] The tags used between the [sort_args] [/sort_args] container will display the parameters used on the previous search (typically on the hitlist return page). The [sort_field] and [sort_order] tags will display values for each instance of the sort parameters used on the previous search. [sort_field] Will display the name of the field used to sort the current found set of records. It is specified as part of a -search or -findall acti on by the [sort_field] tag. [sort_order] Will display the order used for the sort on the current found set of records. It is specified as part of a -search or -findall action by the [sortorder] tag. The sort criteria can be included within an embedded URL as follows: [sort_args]&-sortfield=[sort_field,url]&-sortorder=[sort_order,url][/sort_args]& This is useful when constructing a link that redoes a previous search, when the search used multiple fields to sort the returned set of records. These tags are only valid within the [sort_args] container, and one or both can be used. All HTML appearing between [sort_args] and [/sort_args] is repeated for every field included in the search: [sort_args] Field Used on Sort: [sort_field] Order: [sort_order] [/sort_args] These tags accept the optional parameter that prevents Lasso from applying HTML character encoding. The parameter can also be used to specify URL encoding. If omitted, HTML encoding is per formed by default. Display Sort FieldC Sub-ContainerD [sort_field] (The [sort_field] tag will display the name of the field used to sort the current found set of records. It is specified as part of a search find all action by the [sortfield] tag. This tag is only valid within the [sort_args] [/sort_args] container; refer to that tag for more information. JMDisplays the name of the field used to sort the current found set of records.L [sort_field]NVOnly valid within the [sort_args] [/sort_args] container. Accepts encoding parameters.O [FMP-SortFieldItem]P [sort_field] 6[sort_field] The [sort_field] tag will display the name of the field used to sort the current found set of records. It is specified as part of a search find all action by the [sortfield] tag. This tag is only valid within the [sort_args] [/sort_args] container; refer to that tag for more information. Display Sort OrderC Sub-ContainerD [sort_order] QThe [sort_order] sub-container tag will display the order used for the sort on the current found set of records. This tag is only valid within the [sort_args] [/sort_args] container; refer to that tag for more information. The [sort_order] and [sort_args] tags are used as part of a search find all action by the -sortorder tag. JIDisplays the order used for the sort on the current found set of records.L [sort_order]NVOnly valid within the [sort_args] [/sort_args] container. Accepts encoding parameters.O [FMP-SortOrderItem]P [sort_order] _[sort_order] The [sort_order] sub-container tag will display the order used for the sort on the current found set of records. This tag is only valid within the [sort_args] [/sort_args] container; refer to that tag for more information. The [sort_order] and [sort_args] tags are used as part of a search find all action by the -sortorder tag. Sort FieldC CommandD -sortfield The -sortfield tag tells Lasso which field to sort the results on. This command is optional. Records will be left unsorted if the -sortfield tag is not used, or is not given a value. The value of unsorted (not case-sensitive) is an option that is recognized by Lasso to leave records unsorted. Any number of fields can be included (as long as they appear on the referenced FileMaker Pro layout). To have several fields used in a sort, list multiple -sortfield tags on your format file. The sorts will be nested in the order in which they appear in the HTML. In other words, the first one becomes the primary sort, the next is the secondary sort, and so on. For example, if the primary sort is a field and the next a last name field, then the records returned would be sorted by the city field, and then by the last name within particular cities. Multiple sorts can also be accomplished using a scrolling list and holding down the command key to make multiple field name r selections, or by using a checkbox selection list. If the sort order is indicated, the -sortorder tags apply to the -sortfield tag that appears immediately before it. There can be -sortorder tags for any or all of the -sortfield tags. The value of the -sortorder tag can be returned to the reply page using the [sort_args] [sort_field] [/sort_args] container tag. J)Specifies which field to sort results on.L -sortfieldO -SortFieldP <select name="-sortfield" size=1> <option selected>unsorted <option value="YourFieldName1">text1 <option value="YourFieldName2">text2 <option value="YourFieldName3">text3 <option value="YourFieldName4">text4 </select> <select name="-sortfield" size=1> <option selected>unsorted <option value="YourFieldName1">text1 <option value="YourFieldName2">text2 <option value="YourFieldName3">text3 <option value="YourFieldName4">text4 </select> The -sortfield tag tells Lasso which field to sort the results on. This command is optional. Records will be left unsorted if the -sortfield tag is not used, or is not given a value. The value of unsorted (not case-sensitive) is an option that is recognized by L asso to leave records unsorted. Any number of fields can be included (as long as they appear on the referenced FileMaker Pro layout). To have several fields used in a sort, list multiple -sortfield tags on your format file. The sorts will be nested in the order in which they appear in the HTML. In other words, the first one becomes the primary sort, the next is the secondary sort, and so on. For example, if the primary sort is a field and the next a last name field, then the rec ords returned would be sorted by the city field, and then by the last name within particular cities. Multiple sorts can also be accomplished using a scrolling list and holding down the command key to make multiple field name selections, or by using a checkbox selection list. If the sort order is indicated, the -sortorder tags apply to the -sortfield tag that appears immediately before it. There can be -sortorder tags for any or all of the -sortfield tags. The value of the -sortDjorder tag can be returned to the reply page using the [sort_args] [sort_field] [/sort_args] container tag. Sort OrderC CommandD -sortorder The -sortorder tag applies to the -sortfield tag that appears immediately before it. It is reset to ascending for subsequent sort fields. This command tag is optional. The default sort order is ascending if none are indicated. Any option can be included as a hidden field to predetermine the sort order. The values of ascending, descending, custom (not case-sensitive) are recognized by Lasso to determine how to sort the results of a search. Custom sorting is the same as the File 9Maker Pro sort option Custom order based on value list using the value list that is specified for that field on the layout being referenced (thus, the field must have a value list). The value of the -sortorder tag can be returned to the reply page using the [sort_args] [sort_order] [/sort_args] container tag. Specifies the sort order.L -sortorderO -SortOrderPh<select name="-sortorder"> <option selected>ascending <option>descending <option>custom </select> <select name="-sortorder"> <option selected>ascending <option>descending <option>custom </select> The -sortorder tag applies to the -sortfield tag that appears immediately before it. It is reset to ascending for subsequent sort fields. This command tag is optional. The default sort order is ascending if none are indicated. Any option can be included as a hidden field to predetermine the sort order. The values of ascending, descending, custom (not case-sensitive) are re cognized by Lasso to determine how to sort the results of a search. Custom sorting is the same as the FileMaker Pro sort option Custom order based on value list using the value list that is specified for that field on the layout being referenced (thus, the field must have a value list). The value of the -sortorder tag can be returned to the reply page using the [sort_args] [sort_order] [/sort_args] container tag. String ConcatenateC SubstitutionD [string_concatenate: ...] The [string_concatenate: ] substitution tag is a string tag, and as such is part of a Lasso Module that allows for the manipulation of a specified string of text. The tags in this module can only be used if the String_Tags.mod file is present in the Lasso Modules folder when Lasso is initially launched. This tag concatenates together any number of unnamed parameters. These unnamed parameters are simply values that are not associated with another parameter or tag, for example, in a ame=value pair. The unnamed parameters values can be any literal text or a Lasso substitution tag. Within the [string_concatenate: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_concatenate: one string", another string."] Output: one stringanother string. [string_concatenate: one string", another string."] Output: one string another string. J.Concatenates any number of unnamed parameters.L [string_concatenate: ...]N Multiple unnamed parameters.P4[string_concatenate: "StringText", "MoreStringText"] [string_concatenate: "StringText", "MoreStringText"] The [string_concatenate: ] substitution tag is a string tag, and as such is part of a Lasso Module that allows for the manipulation of a specified string of text. The tags in this module can only be used if the String_Tags.mod file is present in the Lasso Modules folder when Lasso is initially launched. This tag concatenates together any number of unnamed parameters. These unnamed parameters are simply values that are not associat ed with another parameter or tag, for example, in a name=value pair. The unnamed parameters values can be any literal text or a Lasso substitution tag. Within the [string_concatenate: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_concatenate: one string", another string."] Output: one stringanother string. [string_concatenate: one string", another string."] OuC#tput: one string another string. String Count FieldsC SubstitutionD [string_countfields: ...] The [string_countfields: ] tag is part of the String_Tags.mod module. This substitution tag returns a number value for the total number of fields in all of the specified text strings together. A field is a specified location in the string. It is defined as any text or numbers that are found between a specified delimiter. It does NOT output the number of fields of the concatenated parameter string, but evaluates each separately and totals the results. The text string specified in t he tag can contain multiple unnamed parameters. The optional parameter delimiter specifies the character or characters to be used as the delimiter between words. The default delimiter is a space. If no delimiter is specified, all words (or any text separated by a space) are counted. The unnamed parameter and the delimiter value can be any literal text or a Lasso substitution tag. Within the [string_countfields: ] tag, each parameter is separated by commas, and all literal text is surrou nded by quotes (Lasso tags should not be within quotes). Some examples: [string_countfields: "a sample string"] Output: 3 [string_countfields: "one sample string", "another sample string"] Output: 6 [string_countfields: one sample string", " another sample string"] Output: 7 [string_countfields: delimiter="s", one sample string", " another sample string"] Output: 6 [string_countfields: delimiter="sam", one sample string", " another sample string"] Output: 4 JQReturns the total number of fields in all of the specified text strings together.L [string_countfields: ...]N+delimiter, and multiple unnamed parameters.PB[string_countfields: delimiter="DelimiterText", "StringText", ...] [string_countfields: delimiter="DelimiterText", "StringText", ...] The [string_countfields: ] tag is part of the String_Tags.mod module. This substitution tag returns a number value for the total number of fields in all of the specified text strings together. A field is a specified location in the string. It is defined as any text or numbers that are found between a specified delimiter. It does NOT output the number of fields of the concatenated parameter string, but evaluates each separately and totals the results. The text string specified in the tag can contain multiple unnamed parameters. The optional parameter delimiter specifies the character or characters to be used as the delimiter between words. The default delimiter is a space. If no delimiter is specified, all words (or any text separated by a space) are counted. The unnamed parameter and the delimiter value can be any literal text or a Lasso substitution tag. Within the [string_countfields: ] tag, e ach parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_countfields: "a sample string"] Output: 3 [string_countfields: "one sample string", "another sample string"] Output: 6 [string_countfields: one sample string", " another sample string"] Output: 7 [string_countfields: delimiter="s", one sample string", " another sample string"] Output: 6 [string_countfields: delimiter="sam", D8one sample string", " another sample string"] Output: 4 String ExtractC SubstitutionD [string_extract: ...] The [string_extract: ] tag is part of the String_Tags.mod module. This substitution tag extracts a specified range of characters from the source string. The [string_extract: ] tag uses the required parameters start_position and end_position and the unnamed parameter to be evaluated. The unnamed parameter value can be any literal text or a Lasso substitution tag. Within the [string_extract: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes ( Lasso tags should not be within quotes). start_position is the number of characters from the start of the string and end_position is the numbered position of the last character. These characters, plus any found between, are used as the output. If the start_position equals the end_position then only one character would be extracted. Some examples: [string_extract: start_position=1, end_position=1, "yadda1yadda2yadda3yadda4yadda5yadda"] Output: [string_extract: start math-add@ token@ CV_position=7, end_position=11, "yadda1yadda2yadda3yadda4yadda5yadda"] Output: yadda J@Extracts a specified range of characters from the source string.L [string_extract: ...]N7start_position, end_position, and an unnamed parameter.P@[string_extract: start_position=#, end_position=#, "StringText"] [string_extract: start_position=#, end_position=#, "StringText"] The [string_extract: ] tag is part of the String_Tags.mod module. This substitution tag extracts a specified range of characters from the source string. The [string_extract: ] tag uses the required parameters start_position and end_position and the unnamed parameter to be evaluated. The unnamed parameter value can be any literal text or a Lasso substitution tag. Within the [string_extract: ] tag, each parameter is s eparated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). start_position is the number of characters from the start of the string and end_position is the numbered position of the last character. These characters, plus any found between, are used as the output. If the start_position equals the end_position then only one character would be extracted. Some examples: [string_extract: start_position=1, end_position=1, "yadda1yadC da2yadda3yadda4yadda5yadda"] Output: [string_extract: start_position=7, end_position=11, "yadda1yadda2yadda3yadda4yadda5yadda"] Output: yadda String Find PositionC SubstitutionD [string_findposition: ...] The [string_findposition: ] tag is part of the String_Tags.mod module. This substitution tag returns the position of the beginning of the search string. The tag will return the value of 1 if the string is not found. The tag contains a required parameter, find, and an unnamed parameter. The parameter is the set of characters, or string pattern, to search for. The optional start_position and end_position tags can be used to evaluate only a sub-section of the specified string These parameters can be any literal text or a Lasso substitution tag. Within the [string_findposition: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_findposition: find="yadda", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: 1 [string_findposition: find="2", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: 12 [string_findposition: start_position=7, find="yadda", "yadda1 yadda2yadda3yadda4yadda5yadda"] Output: 7 [string_findposition: start_position=5, end_position=11, find="2", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: -1 J>Returns the numeric position of beginning of specified text. L [string_findposition: ...]N<find, start_position,end_position, and an unnamed parameter.P4[string_findposition: find="FindText", "StringText"] [string_findposition: find="FindText", "StringText"] The [string_findposition: ] tag is part of the String_Tags.mod module. This substitution tag returns the position of the beginning of the search string. The tag will return the value of 1 if the string is not found. The tag contains a required parameter, find, and an unnamed parameter. The parameter is the set of characters, or string pattern, to search for. The optional start_position and end_position tags can be used to evaluate only a sub-section of the specified string. These parameters can be any literal text or a Lasso substitution tag. Within the [string_findposition: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_findposition: find="yadda", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: 1 [string_findposition: find="2", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: 12 [stringC _findposition: start_position=7, find="yadda", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: 7 [string_findposition: start_position=5, end_position=11, find="2", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: -1 String Get FieldC SubstitutionD [string_getfield: ...] The [string_getfield: ] tag is part of the String_Tags.mod module. This substitution tag returns the text value of a field. field is a specified location in the string, it is defined as any text or numbers that are found between a specified delimiter. The default delimiter is a space, thus, if no delimiter is specified, the field is every word. The tag is made up of a required parameter field_number and an unnamed parameter. The field_number parameter is a number that specif ies which instance of the field to get (it can be a Lasso substitution tag that results in a number). The optional parameter delimiter specifies the character or characters to be used as the delimiter between words. The unnamed parameter and the delimiter value can be any literal text or a Lasso substitution tag. Within the [string_getfield: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples [string_getfield: "string of text", field_number=3] Output: r [string_getfield: "string of text", field_number=2, delimiter= Output: of [string_getfield: "1yadda2yadda3yadda4yadda5yadda", field_number=1, delimiter="yadda"] Output: 1 [string_getfield: "this is the text", field_number=2] Output: h J"Returns the text value of a field.L [string_getfield: ...]N2field_number, delimiter, and an unnamed parameter.PK[string_getfield: field_number=#, delimiter="DelimiterText", "StringText" ] [string_getfield: field_number=#, delimiter="DelimiterText", "StringText" ] The [string_getfield: ] tag is part of the String_Tags.mod module. This substitution tag returns the text value of a field. field is a specified location in the string, it is defined as any text or numbers that are found between a specified delimiter. The default delimiter is a space, thus, if no delimiter is specified, the field is every word. The tag is made up of a required parameter field_number nd an unnamed parameter. The field_number parameter is a number that specifies which instance of the field to get (it can be a Lasso substitution tag that results in a number). The optional parameter delimiter specifies the character or characters to be used as the delimiter between words. The unnamed parameter and the delimiter value can be any literal text or a Lasso substitution tag. Within the [string_getfield: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_getfield: "string of text", field_number=3] Output: r [string_getfield: "string of text", field_number=2, delimiter= Output: of [string_getfield: "1yadda2yadda3yadda4yadda5yadda", field_number=1, delimiter="yadda"] Output: 1 [string_getfield: "this is the text", field_number=2] Output: h String InsertC SubstitutionD [string_insert: ...] The [string_insert: ] tag is part of the String_Tags.mod module. This substitution tag inserts the specified string into the source string at a specified position. The [string_insert: ] tag uses the required parameters and the unnamed parameter to be evaluated. These parameters can be any literal text or a Lasso substitution tag. The optional position parameter indicates where the insertion is to occur. If position is not specified, the text is inserted at the start of the s tring. Each parameter is surrounded by quotes and separated by commas. Within the [string_insert: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_insert: text="INSERTED", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: INSERTEDyadda1yadda2yadda3yadda4yadda5yadda [string_insert: text="INSERTED", position=5, "yadda1yadda2yadda3yadda4yadda5yadda"] Output: yaddaINSERTED1C yadda2yadda3yadda4yadda5yadda JLInserts the specified string into the source string at a specified position.L [string_insert: ...]N)text, position, and an unnamed parameter.P<[string_insert: position=#, text="InsertText", "StringText"] [string_insert: position=#, text="InsertText", "StringText"] The [string_insert: ] tag is part of the String_Tags.mod module. This substitution tag inserts the specified string into the source string at a specified position. The [string_insert: ] tag uses the required parameters and the unnamed parameter to be evaluated. These parameters can be any literal text or a Lasso substitution tag. The optional position parameter indicates where the insertion is to occur. If position is not specified, the text is inserted at the start of the string. Each parameter is surrounded by quotes and separated by commas. Within the [string_insert: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_insert: text="INSERTED", "yadda1yadda2yadda3yadda4yadda5yadda"] Output: INSERTEDyadda1yadda2yadda3yadda4yadda5yadda [string_insert: text="INSERTED", position=5, "yadd C\a1yadda2yadda3yadda4yadda5yadda"] Output: yaddaINSERTED1yadda2yadda3yadda4yadda5yadda String LengthC SubstitutionD [string_length: ...] The [string_length: ] tag is part of the String_Tags.mod module. This substitution tag outputs the total number of characters in all parameter strings combined. The text string specified in the tag can contain multiple unnamed parameters. The value of an unnamed parameter can be any literal text or a Lasso substitution tag. Within the [string_length: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). e examples: [string_length: "a string", lasso_action] (assume that lasso_action is search Output: 14 [string_length: "123456", "123456"] Output: 12 J6Totals the number of characters of a specified string.L [string_length: ...]N Multiple unnamed parameters.P [string_length: "StringText"] [string_length: "StringText"] The [string_length: ] tag is part of the String_Tags.mod module. This substitution tag outputs the total number of characters in all parameter strings combined. The text string specified in the tag can contain multiple unnamed parameters. The value of an unnamed parameter can be any literal text or a Lasso substitution tag. Within the [string_length: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags shoB uld not be within quotes). Some examples: [string_length: "a string", lasso_action] (assume that lasso_action is search Output: 14 [string_length: "123456", "123456"] Output: 12 String Lower CaseC SubstitutionD [string_lowercase: ...] The [string_lowercase: ] tag is part of the String_Tags.mod module. This substitution tag outputs the specified text in lowercase letters, with all specified text concatenated together into one string. The tag can contain multiple unnamed parameters. The value of an unnamed parameter can be either any literal text or a Lasso substitution tag. Within the [string_lowercase: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not b e within quotes). Some examples: [string_lowercase: "THIS is sOME TEXT", " and SOMe more TEXt"] Output: this is some text and some more text [string_lowercase: "THIS is sOME TEXT", " ", "and SOMe more TEXt"] Output: this is some text and some more text J=Concatenates all specified text and returns it in lowercase. L [string_lowercase: ...]N Multiple unnamed parameters.P [string_lowercase: "StringText"] [string_lowercase: "StringText"] The [string_lowercase: ] tag is part of the String_Tags.mod module. This substitution tag outputs the specified text in lowercase letters, with all specified text concatenated together into one string. The tag can contain multiple unnamed parameters. The value of an unnamed parameter can be either any literal text or a Lasso substitution tag. Within the [string_lowercase: ] tag, each parameter is separated by commas, and all literal text is surrounded +by quotes (Lasso tags should not be within quotes). Some examples: [string_lowercase: "THIS is sOME TEXT", " and SOMe more TEXt"] Output: this is some text and some more text [string_lowercase: "THIS is sOME TEXT", " ", "and SOMe more TEXt"] Output: this is some text and some more text String RemoveC SubstitutionD [string_remove: ...] The [string_remove: ] tag is part of the String_Tags.mod module. This substitution tag removes a specified range of characters from the source string. The [string_remove: ] tag uses the required parameters start_position and end_position and the unnamed parameter to be evaluated. This value can be any literal text or a Lasso substitution tag. Within the [string_remove: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). start_position is the number of characters from the start of the string and end_position is the numbered position of the last character. These characters plus any found between are removed from the string, and the remainder is output. If the start_position equals the end_position then nothing is removed. Some examples: [string_remove: start_position=1, end_position=1, yadda1yadda2yadda3yadda4yadda5yadda"] Output: adda1yadda2yadda3yadda4yadda5yadda [string_remove: start_position=7, end_position=11, "yadda1yadda2yadda3yadda4yadda5yadda"] Output: yadda12yadda3yadda4yadda5yadda [string_remove: start_position=7, end_position=11, "yadda1yadda2yadda3"] Output: yadda12yadda3 [string_remove: start_position=7, end_position=11, "yadda1yadda2yadda3", "yadda9yadda0"] Output: yadda12yadda3yadda9yadda0 J?Removes a specified range of characters from the source string.L [string_remove: ...]N7start_position, end_position, and an unnamed parameter.P>[string_remove: start_position=# end_position=#, "StringText"] [string_remove: start_position=# end_position=#, "StringText"] The [string_remove: ] tag is part of the String_Tags.mod module. This substitution tag removes a specified range of characters from the source string. The [string_remove: ] tag uses the required parameters start_position and end_position and the unnamed parameter to be evaluated. This value can be any literal text or a Lasso substitution tag. Within the [string_remove: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). start_position is the number of characters from the start of the string and end_position is the numbered position of the last character. These characters plus any found between are removed from the string, and the remainder is output. If the start_position equals the end_position then nothing is removed. Some examples: [string_remove: start_position=1, end_position=1, yadda1yadda2yadda3ya dda4yadda5yadda"] Output: adda1yadda2yadda3yadda4yadda5yadda [string_remove: start_position=7, end_position=11, "yadda1yadda2yadda3yadda4yadda5yadda"] Output: yadda12yadda3yadda4yadda5yadda [string_remove: start_position=7, end_position=11, "yadda1yadda2yadda3"] Output: yadda12yadda3 [string_remove: start_position=7, end_position=11, "yadda1yadda2yadda3", "yadda9yadda0"] Output: yadda12yadda3yadda9yadda0 String Remove LeadingC SubstitutionD [string_removeleading: ...] The [string_removeleading: ] tag is part of the String_Tags.mod module. This substitution tag removes all occurrences of a specified pattern that are found at the beginning of all specified parameter strings. The resulting string includes all of the evaluated text concatenated together. There is one required parameter, pattern, which specifies the text to be removed; for example, pattern= will remove all leading spaces. The tag can contain multiple unnamed parameters, each of which will be evaluated. The parameters can be any literal text or a Lasso substitution tag. Within the [string_removeleading: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_removeleading: pattern=" ", " and then some text", " some more text"] Output: and then some textsome more text [string_removeleading: pattern="123", "1231234123and then some text", "12312312some more C; text"] Output: 4123and then some text12some more text JoRemoves all occurrences of a specified pattern which are found at the beginning of specified parameter strings.L [string_removeleading: ...]N)pattern, and multiple unnamed parameters.P@[string_removeleading: pattern="PatternText", "StringText", ...] [string_removeleading: pattern="PatternText", "StringText", ...] The [string_removeleading: ] tag is part of the String_Tags.mod module. This substitution tag removes all occurrences of a specified pattern that are found at the beginning of all specified parameter strings. The resulting string includes all of the evaluated text concatenated together. There is one required parameter, pattern, which specifies the text to be removed; for example, pattern= will remove all leading spac es. The tag can contain multiple unnamed parameters, each of which will be evaluated. The parameters can be any literal text or a Lasso substitution tag. Within the [string_removeleading: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_removeleading: pattern=" ", " and then some text", " some more text"] Output: and then some textsome more text [string_removeleading:C} pattern="123", "1231234123and then some text", "12312312some more text"] Output: 4123and then some text12some more text String Remove TrailingC SubstitutionD [string_removetrailing: ...] The [string_removetrailing: ] tag is part of the String_Tags.mod module. This substitution tag removes all occurrences of a specified pattern that is found at the end of the parameter strings. The resulting string includes all of the evaluated text concatenated together. There is one required parameter pattern which specifies the text to be removed, for example, pattern= will remove all leading spaces. The tag can contain multiple unnamed parameters, each of which will be evaluated . The parameters can be any literal text or a Lasso substitution tag. Within the [string_removetrailing: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). An example is as follows (all trailing spaces are removed): [string_removetrailing: pattern=" ", "and then some text ", "some more text "] Output: and then some textsome more text Another example: [string_removetrailing: "and then some tex Cjt1234123123", pattern="123", "some more text123123123"] Output: and then some text1234some more text JbRemoves all occurrences of a specified pattern which is found at the end of the parameter strings.L [string_removetrailing: ...]N)pattern, and multiple unnamed parameters.PA[string_removetrailing: pattern="PatternText", "StringText", ...] [string_removetrailing: pattern="PatternText", "StringText", ...] The [string_removetrailing: ] tag is part of the String_Tags.mod module. This substitution tag removes all occurrences of a specified pattern that is found at the end of the parameter strings. The resulting string includes all of the evaluated text concatenated together. There is one required parameter pattern which specifies the text to be removed, for example, pattern= will remove all leading spaces. The tag can c ontain multiple unnamed parameters, each of which will be evaluated. The parameters can be any literal text or a Lasso substitution tag. Within the [string_removetrailing: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). An example is as follows (all trailing spaces are removed): [string_removetrailing: pattern=" ", "and then some text ", "some more text "] Output: and then some textsome more C Another example: [string_removetrailing: "and then some text1234123123", pattern="123", "some more text123123123"] Output: and then some text1234some more text String ReplaceC SubstitutionD [string_replace: ...] The [string_replace: ] tag is part of the String_Tags.mod module. This substitution tag replaces some specified text with other specified text. The resulting string includes all of the evaluated text concatenated together. There are three named parameters: find, replace, and and any number of unnamed parameters to be evaluated. The tag will replace one or more occurrences of the string with the replace string for each unnamed parameter. The parameters can be describ ed as follows: The set of characters, or string pattern, to search for. It must be specified. replace The set of characters which will be substituted for the string. If the replace parameter is not defined, the default replace string is a space. With a space, all occurrences of the string are deleted. The replace value that first follows a value is the one used. The number of occurrences to be found and replaced. The default value f or this parameter is which replaces every occurrence of the string with the replace string. The parameters can be any literal text or a Lasso substitution tag. Within the [string_replace: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_replace: find="ano", replace="_", "another string another day"] Output: _other string _other day [string_replace: find="an ", replace="THIS IS REPLACED", "another string another day"] Output: THIS IS REPLACEDother string THIS IS REPLACEDother day [string_replace: find="an", "another string another day"] Output: other string other day [string_replace: find="an", replace="DA", "another string another day", " more stuff to test an"] Output: DAother string DAother day more stuff to test DA J9Replaces specified text with specified replacement text.L [string_replace: ...] N4find, replace, num, and multiple unnamed parameters.PF[string_replace: find="FindText", replace="ReplaceText", "StringText"] [string_replace: find="FindText", replace="ReplaceText", "StringText"] The [string_replace: ] tag is part of the String_Tags.mod module. This substitution tag replaces some specified text with other specified text. The resulting string includes all of the evaluated text concatenated together. There are three named parameters: find, replace, and and any number of unnamed parameters to be evaluated. The tag will replace one or more occurrences of the string with the string for each unnamed parameter. The parameters can be described as follows: The set of characters, or string pattern, to search for. It must be specified. replace The set of characters which will be substituted for the string. If the replace parameter is not defined, the default replace string is a space. With a space, all occurrences of the string are deleted. The replace value that first follows a value is the one used. The number of occurrences to be found and replaced. The default value for this parameter is which replaces every occurrence of the string with the replace string. The parameters can be any literal text or a Lasso substitution tag. Within the [string_replace: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not be within quotes). Some examples: [string_replace: find="ano", replace="_", "another string anothe r day"] Output: _other string _other day [string_replace: find="an", replace="THIS IS REPLACED", "another string another day"] Output: THIS IS REPLACEDother string THIS IS REPLACEDother day [string_replace: find="an", "another string another day"] Output: other string other day [string_replace: find="an", replace="DA", "another string another day", " more stuff to test an"] Output: DAother string DAother day more stuff to test DA String Upper CaseC SubstitutionD [string_uppercase: ...] The [string_uppercase: ] tag is part of the String_Tags.mod module. This substitution tag outputs the specified text in uppercase letters, with all specified text concatenated together into one string. The tag can contain multiple unnamed parameters. The value of an unnamed parameter can be either any literal text or a Lasso substitution tag. Within the [string_uppercase: ] tag, each parameter is separated by commas, and all literal text is surrounded by quotes (Lasso tags should not b e within quotes). Some examples: [string_uppercase: "THIS is sOME TEXT", " and SOMe more TEXt"] Output: THIS IS SOME TEXT AND SOME MORE TEXT [string_uppercase: "THIS is sOME TEXT", " ", "and SOMe more TEXt"] Output: THIS IS SOME TEXT AND SOME MORE TEXT J=Concatenates all specified text and returns it in uppercase. L [string_uppercase: ...]N Multiple unnamed parameters.P [string_uppercase: "StringText"] [string_uppercase: "StringText"] The [string_uppercase: ] tag is part of the String_Tags.mod module. This substitution tag outputs the specified text in uppercase letters, with all specified text concatenated together into one string. The tag can contain multiple unnamed parameters. The value of an unnamed parameter can be either any literal text or a Lasso substitution tag. Within the [string_uppercase: ] tag, each parameter is separated by commas, and all literal text is surrounded 0by quotes (Lasso tags should not be within quotes). Some examples: [string_uppercase: "THIS is sOME TEXT", " and SOMe more TEXt"] Output: THIS IS SOME TEXT AND SOME MORE TEXT [string_uppercase: "THIS is sOME TEXT", " ", "and SOMe more TEXt"] Output: THIS IS SOME TEXT AND SOME MORE TEXT TimeoutC CommandD -timeout The -timeout tag sets the timeout value, that is, the time that Lasso.acgi will wait for a response from FileMaker Pro. It is generally not needed and is optional. If the tag is not used, the default is 60 seconds. The value is measured in seconds and can be a minimum of 10 and a maximum of 300 (5 minutes). The -timeout tag does not apply to the Lasso Plug-in or Lasso Server versions (the timeout value is controlled by the server application in these cases). The timeout setting controls o 1nly the time Lasso will wait for a response from FileMaker Pro. Your Web server also will have a timeout setting that applies to Lasso or any other CGI. For example, for WebSTAR, the default CGI timeout is one minute. You may need to increase your Web server s CGI timeout if you increase Lasso s timeout. JJSets the time that Lasso.acgi will wait for a response from FileMaker Pro.L -timeoutO"(not needed, is FM Pro preference)P/<input type="hidden" name="-timeout" value=120> <input type="hidden" name="-timeout" value=120> The -timeout tag sets the timeout value, that is, the time that Lasso.acgi will wait for a response from FileMaker Pro. It is generally not needed and is optional. If the tag is not used, the default is 60 seconds. The value is measured in seconds and can be a minimum of 10 and a maximum of 300 (5 minutes). The -timeout tag does not apply to the Lasso Plug-in or Lasso Server versions (the timeout value is controlled by the server application b in these cases). The timeout setting controls only the time Lasso will wait for a response from FileMaker Pro. Your Web server also will have a timeout setting that applies to Lasso or any other CGI. For example, for WebSTAR, the default CGI timeout is one minute. You may need to increase your Web server s CGI timeout if you increase Lasso s timeout. A Set TokenC CommandD -token token can be used to pass a value from one format file to the next without being saved in a database. A new token is set using the -token command tag. After a token is set, Lasso will substitute the value for the token into the reply format file in place of the [token_value] tag. To pass the token to a subsequent page, it must be set on each Lasso action, except that Lasso will automatically copy the value into links created for the [detail_link: ], [next], and [prev] tags. A token is typically set to either the contents of a FileMaker field, an entered value, or to the record ID to keep track of a particular record in the FileMaker Pro database. It could also be a literal value, though there is not much sense to that. A token is limited to 255 characters. The syntax for setting a token is: <input type=hidden name="-token value="some value"> When using a field value it would take the form: <input type=hidden name="-token value="[field:"fieldname"]"> When the token is to be entered on a form using a standard input field, the following can be used: <input type="text name="-token size=30> It can selected from a pop-up using: <select name="-token size=1> <option>token value1 <option>token value2 <option>token value3 </select> Tokens can also be set within an embedded URL, for example as: <a href="/Lasso.acgi?-database=Products.fp3&-layout=Layout1&-token=[recid_value]&[response]=productlist.html&-show">Browse our producDrts</a> This example can only be used on a post-Lasso file that substitutes a valid record ID value into the link. JaPasses a value from one format file to the next without passing through a FileMaker Pro database.L -tokenO -TokenP5<input type="hidden" name="-token" value="SomeValue"> <input type="hidden" name="-token" value="SomeValue"> token can be used to pass a value from one format file to the next without being saved in a database. A new token is set using the -token command tag. After a token is set, Lasso will substitute the value for the token into the reply format file in place of the [token_value] tag. To pass the token to a subsequent page, it must be set on each Lasso action, except that Lasso will automatically copy the value into links created for th e [detail_link: ], [next], and [prev] tags. A token is typically set to either the contents of a FileMaker field, an entered value, or to the record ID to keep track of a particular record in the FileMaker Pro database. It could also be a literal value, though there is not much sense to that. A token is limited to 255 characters. The syntax for setting a token is: <input type=hidden name="-token value="some value"> When using a field value it would take the form: <input type=hi dden name="-token value="[field:"fieldname"]"> When the token is to be entered on a form using a standard input field, the following can be used: <input type="text name="-token size=30> It can selected from a pop-up using: <select name="-token size=1> <option>token value1 <option>token value2 <option>token value3 </select> Tokens can also be set within an embedded URL, for example as: <a href="/Lasso.acgi?-database=Products.fp3&-layout=Layout1&-token=[recid_valuD e]&[response]=productlist.html&-show">Browse our products</a> This example can only be used on a post-Lasso file that substitutes a valid record ID value into the link. Display Token ValueC SubstitutionD [token_value] If a token has been set using the -token tag, Lasso will substitute [token_value] for the value of the token on the reply page. To pass the token value to subsequent format files, you will need to set the token again. Setting a token to the [token_value] allows you to pass along the value from one format file to another. To set the token to the token_value, the following syntax is used: <input type="hidden name="-token value="[token_value]"> If the value of the token is needed within an inline statement on the directly returned response format file, it needs to be set again. The following syntax is used to set a token within an inline: [inline: database="YourDBName", layout="YourLayoutName", token=token_value, search] Here is the token value: [token_value] [/inline] The [token_value] tag accepts the optional parameters smart, break, which perform the same functions as they do for the [field] tag. This can be accomplished using the following: )input type=hidden name="-token value="[token_value,raw]"> In an inline the parameter can be included as follows: [inline: database="YourDBName", layout="YourLayoutName", token=(token_value,raw), add] There are no quotes placed around either token token_value since both are Lasso tags. J1Inserts the value of the token on the reply page.L [token_value]N Accepts encoding parameters. [FMP-CurrentToken: [token_value] [token_value] If a token has been set using the -token tag, Lasso will substitute [token_value] for the value of the token on the reply page. To pass the token value to subsequent format files, you will need to set the token again. Setting a token to the [token_value] allows you to pass along the value from one format file to another. To set the token to the token_value, the following syntax is used: <input type="hidden name="-token value="[token_value]"> If the value of the token is needed within an inline statement on the directly returned response format file, it needs to be set again. The following syntax is used to set a token within an inline: [inline: database="YourDBName", layout="YourLayoutName", token=token_value, search] Here is the token value: [token_value] [/inline] The [token_value] tag accepts the optional parameters smart, break, which perform the same functions as they do for the [field] tag. This can be accomplished using the 8following: <input type=hidden name="-token value="[token_value,raw]"> In an inline the parameter can be included as follows: [inline: database="YourDBName", layout="YourLayoutName", token=(token_value,raw), add] There are no quotes placed around either token token_value since both are Lasso tags. Display Total RecordsC SubstitutionD [total_records] The substitution tag [total_records] can be used to display the total number of records in the FileMaker Pro database used in the previous Lasso action. It can be used only on a post-Lasso format file that has been processed by Lasso.JWInserts the total number of records in the database used in the previous Lasso action. L [total_records]O [FMP-CurrentRecordCount]P [total_records]Q [total_records] The substitution tag [total_records] can be used to display the total number of records in the FileMaker Pro database used in the previous Lasso action. It can be used only on a post-Lasso format file that has been processed by Lasso. Update RecordC ActionD -update The -update action updates a specific record in the specified FileMaker Pro database. The sample syntax shows how to submit an update request with a button on an HTML form. When the submit button is selected, Lasso will update the currently displayed record using the current entered items on the form. The update can also occur using an embedded URL link. However, in either case, the -update action must occur on a post-Lasso form since Lasso must first identify the specific record to be u pdated (by retrieving the record ID for a specific record after a Lasso action has identified that record). Also, records can only be updated one at a time; it is not possible to update a group of records listed on a hitlist. In order for an -update action to be performed, the -recid tag must specify the record ID of the record to be updated. The syntax used to direct the action to a specific record is as follows: <input type="hidden name="-recid value="[recid_value]"> The name of th ;e submit button must be -update and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-update"> The name parameter must specify the action, even if the action is specified elsewhere. J(Updates a specific record in a database.L -updateO -EditP:<input type="submit" name="-update" value="Update Record"> <input type="submit" name="-update" value="Update Record"> The -update action updates a specific record in the specified FileMaker Pro database. The sample syntax shows how to submit an update request with a button on an HTML form. When the submit button is selected, Lasso will update the currently displayed record using the current entered items on the form. The update can also occur using an embedded URL link. However, in either case, the -update action must occur on a post-Lasso form since Lasso must first identify the specific record to be updated (by retrieving the record ID for a specific record after a Lasso action has identified that record). Also, records can only be updated one at a time; it is not possible to update a group of records listed on a hitlist. In order for an -update action to be performed, the -recid tag must specify the record ID of the record to be updated. The syntax used to direct the action to a specific record is as follows: <input type=" whidden name="-recid value="[recid_value]"> The name of the submit button must be -update and the value is any text you want to appear on the button. Images may also be used as submit buttons, as in the following example: <input type="Image src="searchgraphic.gif name="-update"> The name parameter must specify the action, even if the action is specified elsewhere. Value ListsC ContainerD [value_list: ...]E [/value_list] The [value_list: [/value_list] tag can be used to display the value list associated with a specific field, or the currently selected items for a specific field. Quotes can be used optionally to surround the name of the field. This tag can be used with any type of selection list, including radio buttons, scrolling lists, checkboxes, and pop-up lists. To display the list vertically, use an HTML line break (<br>) to separate values. A comma may be desired to separate values if the list is displayed horizontally. For example: [value_list:"Markets"] [list_value] , [/value_list] This syntax will display the value list which is assigned to the specified field on the specified layout. All items are displayed whether or not any are currently selected for a specific record. checked selected tags are used to display only those values that are currently selected in the database. If the field is empty (no items are selected) then nothing would be displayed. Using Lasso will return the text checked if an item is selected, and selected will return the word selected. It is used as follows: [value_list:"Tasks"] [list_value, checked] , [/value_list] [value_list:"Tasks"] [list_value, selected] , [/value_list] These tags can also appear separately within their own pair of square brackets. [value_list:"Tasks"] [list_value][checked] , [/value_list] <select name="YourFieldName"> [value_list:"YourFieldName"] <option value="[li st_value] [selected]>[list_value] [/value_list] </select> checked and selected tags are essentially interchangeable when used in conditional statements. To have a conditional statement display selected items only, use the following example: [value_list:"Jobs"][if: checked != "][else][list_value],[/if] [/value_list] [value_list:"Jobs"][if: selected =="selected"][list_value],[else][/if] [/value_list] This will display the comma only after those list values that are checke d. Unfortunately, this will still leave a trailing comma after the last item. To eliminate the trailing comma, the [loop_count] tag can be used to place a comma after all list value items, except the first, as follows: [value_list: category] [if: loop_count != 1], [/if][list_value] [/value_list] Another example: <table border=1> [valuelist:"Programs"] [if: checked =="checked"] <tr><td><b>X</b></td> <td>[list_value]</td></tr>[else] <tr><td> </td> <td>[list_value]</td></F tr>[/if] [/value_list] </table> This will display a table with all items of the value list displayed in their own row. The items that are currently selected will display an to indicate that the value exists for that field in the database. JWDisplays the value list associated with a specific record, or currently selected items.L#[value_list: ...] ... [/value_list]N=Name of the field. Within container: [list_value], [checked]O%[FMP-ValueList: ...] [/FMP-ValueList] PP[value_list:"YourFieldName"] [list_value,checked]<br clear="all"> [/value_list] [value_list:"YourFieldName"] [list_value,checked]<br clear="all"> [/value_list] The [value_list: [/value_list] tag can be used to display the value list associated with a specific field, or the currently selected items for a specific field. Quotes can be used optionally to surround the name of the field. This tag can be used with any type of selection list, including radio buttons, scrolling lists, checkboxes, and pop-up lists. To display the list vertically, use an HTML line break (< br>) to separate values. A comma may be desired to separate values if the list is displayed horizontally. For example: [value_list:"Markets"] [list_value] , [/value_list] This syntax will display the value list which is assigned to the specified field on the specified layout. All items are displayed whether or not any are currently selected for a specific record. checked selected tags are used to display only those values that are currently selected in the database. If the f ield is empty (no items are selected) then nothing would be displayed. Using checked, Lasso will return the text checked if an item is selected, and selected will return the word selected. It is used as follows: [value_list:"Tasks"] [list_value, checked] , [/value_list] [value_list:"Tasks"] [list_value, selected] , [/value_list] These tags can also appear separately within their own pair of square brackets. [value_list:"Tasks"] [list_value][checked] , [/value_list] <select name="YourFieldName"> [value_list:"YourFieldName"] <option value="[list_value] [selected]>[list_value] [/value_list] </select> checked and selected tags are essentially interchangeable when used in conditional statements. To have a conditional statement display selected items only, use the following example: [value_list:"Jobs"][if: checked != "][else][list_value],[/if] [/value_list] [value_list:"Jobs"][if: selected =="selected"][list_value],[else][/if] [/val ue_list] This will display the comma only after those list values that are checked. Unfortunately, this will still leave a trailing comma after the last item. To eliminate the trailing comma, the [loop_count] tag can be used to place a comma after all list value items, except the first, as follows: [value_list: category] [if: loop_count != 1], [/if][list_value] [/value_list] Another example: <table border=1> [valuelist:"Programs"] [if: checked =="checked"] <tr><td><b>X</b></td> Ftd>[list_value]</td></tr>[else] <tr><td> </td> <td>[list_value]</td></tr>[/if] [/value_list] </table> This will display a table with all items of the value list displayed in their own row. The items that are currently selected will display an to indicate that the value exists for that field in the database. Retrieve a VariableC SubstitutionD [var: ...] [This [var: ] tag retrieves the indicated variable for display or to be used within another Lasso tag. The name of the variable is specified within the [set_var: ] tag and can appear any number of times on the same processed format file. If the specified variable has not been set, this outputs nothing. See the [set_var: ] tag for more details. J7Inserts the variables set with the [set_var: ...] tag. L [var: ...] N2Name of the variable. Accepts encoding parameters.P [var: "variablename"] r[var: "variablename"] This [var: ] tag retrieves the indicated variable for display or to be used within another Lasso tag. The name of the variable is specified within the [set_var: ] tag and can appear any number of times on the same processed format file. If the specified variable has not been set, this outputs nothing. See the [set_var: ] tag for more details. WhileC ContainerD [while: ...]E [/while] Whatever text or tags found between the [while: ] and [/while] container will be repeated as long as the specified condition evaluates to true. The [while: ] tag is a cross between the [if: ] and [loop: ] tags. The conditional statement follows the same specifications used with the [if: ] tag. That is, the basic form of the tag is: [while: (comparison-value) operator (comparison-value)] HTML if condition is true [/while] A conditional statement consists of the comparison fields t hat appear on either side of the comparison pair and the operator that determines how to compare those values. The comparison value can either be a hard-coded literal value, a value returned for a FileMaker Pro field, or a Lasso substitution tag. Multiple conditional statements can be combined using the concatenation symbols. See the [If: ] tag for more details. The [loop_count] tag is a useful sub-container tag to use with the [while: ] tag to make a comparison to the cur #rent loop value. For example to have the [while: ] tag repeat until the [loop_count] reaches the number 20: Loop while loop_count <= 20 [while : loop_count <= 20] [loop_count], [/while] In this case, a list of numbers from 1 to 20 will appear, with each number separated by a comma. JJOffers the option to repeat a loop as long as the given condition is true.L [while: ...] ... [/while] The conditional expression made up of a value, operator, and the comparison value. Within the container: what should display repeatedly while conditional is true.P0[while: condition] ...text or tags ... [/while] [while: condition] ...text or tags ... [/while] Whatever text or tags found between the [while: ] and [/while] container will be repeated as long as the specified condition evaluates to true. The [while: ] tag is a cross between the [if: ] and [loop: ] tags. The conditional statement follows the same specifications used with the [if: ] tag. That is, the basic form of the tag is: [while: (comparison-value) operator (comparison-value)] HTML if condition is true [/while] A conditi onal statement consists of the comparison fields that appear on either side of the comparison pair and the operator that determines how to compare those values. The comparison value can either be a hard-coded literal value, a value returned for a FileMaker Pro field, or a Lasso substitution tag. Multiple conditional statements can be combined using the concatenation symbols. See the [If: ] tag for more details. The [loop_count] tag is a useful sub-container tag to use with Uthe [while: ] tag to make a comparison to the current loop value. For example to have the [while: ] tag repeat until the [loop_count] reaches the number 20: Loop while loop_count <= 20 [while : loop_count <= 20] [loop_count], [/while] In this case, a list of numbers from 1 to 20 will appear, with each number separated by a comma. Sort by Tag Sort by Tag Name Sort by Tag Type Sort by Tag Comment From Find to List View Cancel Find Find Button Sort by Tag math-add math-div math-mod math-mult math-round math-sub maxrecords maxrecords value nfound noresults nothing nshown opbegin opend operator option portal inline random recid recid value record referrer referrer repeat value repeating repetition reqfieldmissing required response response scripts search search search field search search value selected server server server cookie skiprecords skiprecords value field order sortfield sortorder string concatenate string countfields string extract string findposition string getfield string insert string length string lowercase string remove string removeleading string removetrailing string replace string uppercase timeout token token value total records update value while Cancel Find Sort by Tag Name Sort by Tag Type Sort by Tag Comment From Find to List View Find Button Helvetica Geneva Times Geometr231 Hv BT Palatino Monaco AGaramond Americana Novarese BoldItalic sub-con ) = 400 OKdify Find if ( fParseT Cancelunsigned char)( b[ i ] ) ] CancelByte1 ) encodeTwoBytes There are no valid criteria in this request. Type a valid request before clicking Find.C+ ) = 0 OKs a 2-byt if ( fParseT Cancelunsigned char)( b[ i ] ) ] = kTwoByte1 ) encodeTwoBytes No records match this request.E+ ) = 1 Novarese Bold Giovanni Bold FPTHA sys:Desktop Folder:Lasso_Tags MSPCA NAMEA Lasso_Tags RPTHA Lasso_Tags alisA Lasso_Tags FMP3FMP3 Desktop Folder sys:Desktop Folder:Lasso_Tags NAMEA LDML Reference Source ZONEA (LIST VDEFA( Tag Type